Lukas_Jackson
Active member
Will see what Evan bring in next updates
Some tx I receive after 20 minutes with 1 confirmation and some with IX
v0.10.17.x Testing
- Thread starter eduffield
- Start date
- Status
Some tx I receive after 20 minutes with 1 confirmation and some with IX
qwizzie
Well-known member
Unfortunely its still a bit wonky on the side of the target wallets, sometimes it gets picked up by masternodes immediately and it will be added
at the total balance of the target wallet but most times it will reach target wallet immediately but without masternodes confirmation after which it
waits for POW confirmations.
edit : all in all the masternodes seem slow to form consensus about InstantX transactions.
edit : i have even seen transactions getting switched forth and back between confirmed and unconfirmed status (appearing and disappearing from total balance)
at the total balance of the target wallet but most times it will reach target wallet immediately but without masternodes confirmation after which it
waits for POW confirmations.
edit : all in all the masternodes seem slow to form consensus about InstantX transactions.
edit : i have even seen transactions getting switched forth and back between confirmed and unconfirmed status (appearing and disappearing from total balance)
Last edited by a moderator:
Lukas_Jackson
Active member
sent again
flare
Well-known member
Local QT segfaulted for me too.
stdout:
Code:stu@stu-laptop:~/.darkcoin$ ./darkcoin-qt --instantxdepth=6 init message: Verifying wallet... init message: Loading block index... init message: Verifying blocks... init message: Loading wallet... init message: Loading addresses... init message: Done loading !!!! USING INSTANTX2 !!!! USING INSTANTX2 QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations() QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations() !!!! USING INSTANTX2 QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations() QMetaObject::invokeMethod: No such method WalletModel::updateConfirmations() Segmentation fault (core dumped)
last few secs of debug.log:
Code:2014-11-28 21:12:39 received block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=20 2014-11-28 21:12:39 CheckBlock() : Couldn't find masternode payment(0|1392857138) or payee(0|n2QgqDT8LP1zBMZdfN2uwubpSURG5wSGJz) nHeight 71197. 2014-11-28 21:12:39 CheckBlock() : Couldn't find masternode payment(0|1392857138) or payee(0|n2QgqDT8LP1zBMZdfN2uwubpSURG5wSGJz) nHeight 71197. 2014-11-28 21:12:40 Committing 2 changed transactions to coin database... 2014-11-28 21:12:40 SetBestChain: new best=00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 height=71197 log2_work=45.905418 tx=157187 date=2014-11-28 21:12:23 progress=1.000000 2014-11-28 21:12:40 received getdata for: block 00000001b9a0c2a0767bd2b303fbba40a3edd2846825924b495547f6b3d02014 peer=3 2014-11-28 21:12:40 received getdata for: block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=3 2014-11-28 21:12:41 received getdata for: block 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=19 2014-11-28 21:12:41 ProcessMessageInstantX::txlreq 2014-11-28 21:12:41 ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 86.20.185.139:19999 /Satoshi:0.10.17.1/ : accepted 9788ccc18017b5a97dff5e3f5cb3b5e13e3d9dab4450f47b56597228fcdf4c93 2014-11-28 21:12:42 send last getblocks for 00000001b9a0c2a0767bd2b303fbba40a3edd2846825924b495547f6b3d02014 peer=18 2014-11-28 21:12:42 send last getblocks for 00000002512656dee5a8d52a36e2e141e4e3b5ac888e82a8d0d8b902f955fb26 peer=18 2014-11-28 21:12:43 getblocks 71197 to 0 limit 500 peer=18 2014-11-28 21:12:43 getblocks -1 to 0 limit 500 peer=18 2014-11-28 21:12:44 dstx: Got Masternode transaction 5b5e3245070fc6ad82ac9cdfd5cd91a6f67a06a856a1a228113be1e0cc004483
DS was hustling along at top speed though.
edit: MN just crashed too. Last line in debug.log:
Code:2014-11-28 21:00:18 Removing old transaction lock c36f5dad03ed0f72bc1b10facee65ad05744a6a141d3636482b09895e197c392
Same for me, v1 dies on
Code:
2014-11-28 22:36:22 Removing old transaction lock
Propulsion
The buck stops here.
So I guess no ones mentioned it and just assumed but it seems that all the seg faults are on Linux. Windows users: are your wallets crashing?
Running 10.17.1 on Windows 10 Tech Preview just fine doing remote / cold storage, wallet is fine and stable, but 1 of two MNs i setup won't stay running.
Lukas_Jackson
Active member
I am on win7 and have a hot MN working fine
Propulsion
The buck stops here.
I guess we know which is the better operating system now.
Lukas_Jackson
Active member
Evan and Gates have a secret agreement
Tough when mn's keep dropping :/
Local/Remote.
Remote tMN setup and running fine~ But about 30 sec later, it crashes..... Have tried many times. But this version is better than last one which i can't evan setup it up and running....
Edit:
Well, after many times trying, this time it seems ok~ but don't know why and how long it will be persistent.
Found that 54.*.*.* tMN was down and then all my tMN are ok, at least till now.
Remote tMN setup and running fine~ But about 30 sec later, it crashes..... Have tried many times. But this version is better than last one which i can't evan setup it up and running....
Edit:
Well, after many times trying, this time it seems ok~ but don't know why and how long it will be persistent.
Found that 54.*.*.* tMN was down and then all my tMN are ok, at least till now.
Last edited by a moderator:
Yah, I'm on Ubuntu and I can't keep my wallet online, let alone set as masternode 
moli
Well-known member
I think a new version is coming soon to fix the crash: https://github.com/darkcoin/darkcoin/commits/instantx
moli
Well-known member
Propulsion, this is why you should write a MN guide for windows users, using Amazon, in your own words and version...
Propulsion, this is why you should write a MN guide for windows users, using Amazon, in your own words and version...
Horrible, horrible idea. The last thing the darkcoin network needs is more windows masternodes.
Waay too many security issues with that OS. ick!
- Status