v0.11.1.x InstantX Testing

Status
Not open for further replies.
eduffield said:
************************************** 11.1.9 ***************************************

Everyone please update to v9 and restart with --reindex, this should work much better!

- Version / Protocol bump
- Improved feedback for IX
- Fixed a couple segfaults
- DS progress bar calculations (Udjin)

Compiling: If you get a 404 please try again in a bit

Source: https://github.com/darkcoin/darkcoin/tree/v0.11.1.x

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...04/gitian-win-darkcoin-bin/32/darkcoin-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...n-osx-darkcoin-dist/darkcoin-0.11.1.9-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...09/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...09/gitian-linux-darkcoin-bin/bin/64/darkcoind
Click to expand...

Evan, when starting with a depth of 60, does that mean locking the transaction for 60 blockchain rounds or minutes? And if so, is it released after wards to the blockchain automatically, is this a kind of crypto timelock setting then?
 
test.p2pool.masternode.io:18998 still down.

Edit:all versions now downloadable ..
 
Last edited by a moderator:
windows version
IX

Status: 5/confirmed (verified via instantx), has not been successfully broadcast yetDate: 2/5/2015 17:57To: Sub-Ether yG466d8XLyemNKQCEZ3RReoLNTGwHpjfqqDebit: -121.00 tDRKTransaction fee: -0.01 tDRKNet amount: -121.01 tDRKTransaction ID: 569544cb9126a8b53b84d05e29467563b83f36e3d10a99d1f5228326c04dacd5-000

Status: 5/confirmed (verified via instantx), has not been successfully broadcast yetDate: 2/5/2015 17:58To: Sub-Ether yG466d8XLyemNKQCEZ3RReoLNTGwHpjfqqDebit: -131.00 tDRKTransaction fee: -0.01 tDRKNet amount: -131.01 tDRKTransaction ID: bcbe0aff79f2cdb59481c602e6cb465a04fc67d2aa8f426f7d729173b6e48838-000

Status: 5/confirmed (verified via instantx), has not been successfully broadcast yetDate: 2/5/2015 17:59To: Sub-Ether yG466d8XLyemNKQCEZ3RReoLNTGwHpjfqqDebit: -141.00 tDRKTransaction fee: -0.01 tDRKNet amount: -141.01 tDRKTransaction ID: 9f829130ec2db750a160b31798e055d8eeb7d30b6b3ebdbbac30280035d82b18-000
 
Disco!! instantX and darksend working together and immediately, its looking verrry good :grin::grin::grin:
I restarted the wallet and got the usual switch from 5/6 to 1/6 confirmations .
Update seems slower especially on none SSD.

upload_2015-2-5_17-5-13.png
 
What does this mean? "Status: 23 confirmations (verified via instantx), has not been successfully broadcast yet" - how has it been confirmed 23 times without having been broadcast?
 
eduffield said:
************************************** 11.1.9 ***************************************

Everyone please update to v9 and restart with --reindex, this should work much better!

- Version / Protocol bump
- Improved feedback for IX
- Fixed a couple segfaults
- DS progress bar calculations (Udjin)

Compiling: If you get a 404 please try again in a bit

Source: https://github.com/darkcoin/darkcoin/tree/v0.11.1.x

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/...04/gitian-win-darkcoin-bin/32/darkcoin-qt.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...n-osx-darkcoin-dist/darkcoin-0.11.1.9-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...09/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/...09/gitian-linux-darkcoin-bin/bin/64/darkcoind
Click to expand...


Main network miner updated.

MN updated..

Thank you evan!!

edit: btw, listening to an interview of Evan at: https://letstalkbitcoin.com/blog/post/beyond-bitcoin-26-darkcoin
 
updated.

I just sent 956 DRK, depth=60, DS+IX... wallet hung for about 8 seconds (1 core VM 1GB ram), and wet through.

Status: 60 confirmations (verified via instantx), has not been successfully broadcast yet
Date: 2/5/15 17:19
To: LucDB88 yEJFAyVVHDmSNDHKxkLZ7PKpYBUK6u3F2U
Debit: -956.00 tDRK
Transaction fee: -0.00956 tDRK
Net amount: -956.00956 tDRK
Transaction ID: b88bc828b2392e5422dc2ebef01b98cb60881995691a71a05173f81b5cf790bd-000
Click to expand...


Again, that seems way too fast for depth=60. I sent that amount to get rid off a few denoms and kick start DS again... which it absolutely did within seconds of sending those funds out. Looking pretty sleek!

.
 
mastermined said:
actually it's about one penny so that's cool! :cool:
sorry, i know this is not the right thread for this. :oops:
thanks to everybody that is testing instantX. very exciting.
Click to expand...
thelonecrouton said:
What does this mean? "Status: 23 confirmations (verified via instantx), has not been successfully broadcast yet" - how has it been confirmed 23 times without having been broadcast?
Click to expand...

I was asking that a while back. As I understand it, and correct me if I'm wrong, the masternode network verified it was valid and put a lock on it (I assume 23 masternodes did) and now it waits for mining confirmation? Which = broadcast? ????
 
TanteStefana said:
I was asking that a while back. As I understand it, and correct me if I'm wrong, the masternode network verified it was valid and put a lock on it (I assume 23 masternodes did) and now it waits for mining confirmation? Which = broadcast? ????
Click to expand...

As I understand things (doesn't mean much ;D) every tx is broadcast immediately, kind of by definition, when you hit Send... ???
 
moli said:
[12:21:22] <coingun> k p2pool is back up
[12:21:27] <coingun> for now
[12:24:08] <coingun> for now lol
Click to expand...
yes working; mining and running a test masternode on the same machine, as it should be, lol.
If its this good with 48 masternodes and limited mining, think what it'll be like on mainnet :wink:
 
I get 5/6 confirmations doing DS+InstantX transaction. 5 confirmations are instant but the 6th takes a few minutes to finish. Should that be instant 6?
 
Ok, so I tried to send and got 0 unconfirmed broadcast through 11 nodes which I don't understand

Then it turned into 1 unconfirmed broadcast through 11 nodes

Shouldn't it say confirmed instead of unconfirmed? makes no sense?

The clock did show up for the "1 unconfirmed" I guess that's instantX working?

EDIT: nevermind, I forgot to click the instantX box (duh) but ah, er, that's what it looks like without instant X ;)

9rnmRv.jpg
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top