cool.. { "SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT" : 1423519981, "SPORK_3_INSTANTX_BLOCK_FILTERING" : 1423519981 }
No problem with higher than 1000 amounts btw : Status: 5/confirmed (verified via instantx), broadcast through 27 node(s) Date: 9-2-2015 23:12 To: y9RuivASms4rLdC1LNHQhsg7YhFTJgCrVR Debit: -1234.5678 tDRK Transaction fee: -0.01 tDRK Net amount: -1234.5778 tDRK Transaction ID: 9af34c2f86a0e5948d2f47cbfbfcc9c3e9aefdb9d7bf715c7e9eb4369fd15820-000 * will just need 1 POW confirmation to get fully confirmed ** eh, and we may need a bit more mining hash power to get to next block ... edit : never mind.. looks like we are moving on again
Sent some DS+IX, but got the error mentioned above. Sender: Status: 0/confirmed (InstantX verification failed), broadcast through 15 node(s) Date: 10.2.2015 г. 00:06 To: test2 yEzvycxnbD26bJ9FhfzQh5XftHVD2V7Ndx Debit: -10.00 tDRK Transaction fee: -0.100101 tDRK Net amount: -10.100101 tDRK Transaction ID: 11971796ba431617a087f2a5b2f651902fc74ede9978ed5e65fe7f0b24f0bd23-000 Receiver: Status: 5/confirmed (verified via instantx) Date: 10.2.2015 г. 00:06From: unknown To: yEzvycxnbD26bJ9FhfzQh5XftHVD2V7Ndx (own address) Credit: 10.00 tDRK Net amount: +10.00 tDRK Transaction ID: 11971796ba431617a087f2a5b2f651902fc74ede9978ed5e65fe7f0b24f0bd23-000
Sender: Status: 6 confirmations (verified via instantx), broadcast through 28 node(s) Date: 10/02/2015 00:09 To: yB72oQzEP1J1CFvcLS8NkcombZxajuye3x Debit: -100.00 tDRKTransaction fee: -0.01 tDRK Net amount: -100.01 tDRK Transaction ID: a8e596353d276d7d0d5ad77acde43b48e43c1a8822186cafc2286eb56ff4c812-000 Receiver: Status: 1/confirmed (InstantX verification failed) Date: 2015-02-10 00:09 From: unknown To: yB72oQzEP1J1CFvcLS8NkcombZxajuye3x (own address, label: Masternode) Credit: 100.00 tDRK Net amount: +100.00 tDRK Transaction ID: a8e596353d276d7d0d5ad77acde43b48e43c1a8822186cafc2286eb56ff4c812-000 Edit: Receiver cannot send coins using IX. Asking for 6 confirmations
Regardless of this, coins appeared almost instantly on the balance. The problem is on the verification side.
yeah, it needs 6 POW confirmations .. right now you only have 1 POW confirmation. You could try selecting another input amount through coin control. See if sending out works then.
wtf? ... this just popped out of the blue in my ssh window!! ... what the heck is this? had to do CTRL+c to get back to prompt! What be this voodoo ?
here is some stuff from my debug.log : noticing some checkblock failures and orphan blocks.. FYI (wallet itself seems to be running fine) 2015-02-09 22:26:22 ProcessBlock: ACCEPTED 2015-02-09 22:26:23 Removing inactive masternode 79.169.179.111:20001 2015-02-09 22:26:23 Removing inactive masternode 79.169.179.111:20005 2015-02-09 22:27:12 CheckBlock() : Couldn't find masternode payment(1|10000000000) or payee(0|yKXk5rYw3Gp8b6dQB5FqvPE3vwYVDkETq4) nHeight 2644. 2015-02-09 22:27:12 ERROR: CheckBlock() : Couldn't find masternode payment or payee 2015-02-09 22:27:12 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-09 22:27:13 mnw - winning vote CTxIn(COutPoint(a965b7a1e5533cfc1caada72899b1f5db83e3b6cb74d61302892ec10f11f2692, 9), scriptSig=) Height 2654 bestHeight 2643 2015-02-09 22:27:13 CheckBlock() : Couldn't find masternode payment(1|10000000000) or payee(0|yKXk5rYw3Gp8b6dQB5FqvPE3vwYVDkETq4) nHeight 2644. 2015-02-09 22:27:13 ERROR: CheckBlock() : Couldn't find masternode payment or payee 2015-02-09 22:27:13 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-09 22:27:13 CheckBlock() : Couldn't find masternode payment(1|10000000000) or payee(0|yKXk5rYw3Gp8b6dQB5FqvPE3vwYVDkETq4) nHeight 2644. 2015-02-09 22:27:13 ERROR: CheckBlock() : Couldn't find masternode payment or payee 2015-02-09 22:27:13 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-09 22:27:23 Removing inactive masternode 79.169.179.111:19999 2015-02-09 22:31:00 CreateNewLock - New Transaction Lock 4d678984171ccd8c1333702fe02da7954b242c5e2efc70ffc638d70d043c53c4 ! 2015-02-09 22:31:00 ProcessMessageInstantX::txlreq - Transaction Lock Request: 128.127.106.235:19999 /Core:0.11.1.18/ : accepted 4d678984171ccd8c1333702fe02da7954b242c5e2efc70ffc638d70d043c53c4 2015-02-09 22:32:23 Removing inactive masternode 80.152.228.67:20001 2015-02-09 22:34:29 CheckBlock() : Skipping masternode payment check - nHeight 2644 Hash 000000063c57eb594b723454cca21636627a24ac8578e1da8cbbe5d9d2568ffc 2015-02-09 22:34:29 ProcessBlock: ORPHAN BLOCK 0, prev=000000053f7aa485e833fbb7c1930b96fae303eccaa67784763488d4642281db 2015-02-09 22:34:29 mnw - winning vote CTxIn(COutPoint(47dc396819b33d2733f580ebcc3f96639f7c96606c2c89f59613d0cb14ef4ef0, 0), scriptSig=) Height 2655 bestHeight 2643 2015-02-09 22:35:35 ResendWalletTransactions() 2015-02-09 22:36:17 mnw - winning vote CTxIn(COutPoint(712f7ab7035912ac2c7b5e6e58feb94f589a6f950eac4e42861066ec95592813, 0), scriptSig=) Height 2656 bestHeight 2643 2015-02-09 22:36:17 CheckBlock() : Skipping masternode payment check - nHeight 2644 Hash 00000003d48d340ac65dcfee11d2bb564244ab99853c9ae386e4f7298baf6dc0 2015-02-09 22:36:17 ProcessBlock: ORPHAN BLOCK 1, prev=000000063c57eb594b723454cca21636627a24ac8578e1da8cbbe5d9d2568ffc 2015-02-09 22:36:39 mnw - winning vote CTxIn(COutPoint(a965b7a1e5533cfc1caada72899b1f5db83e3b6cb74d61302892ec10f11f2692, 16), scriptSig=) Height 2657 bestHeight 2643 2015-02-09 22:36:40 CheckBlock() : Skipping masternode payment check - nHeight 2644 Hash 0000000d64f5a49d668de0dea19646f291ecf0e6d2d878452efa4cfbdcdb673c 2015-02-09 22:36:40 ProcessBlock: ORPHAN BLOCK 2, prev=00000003d48d340ac65dcfee11d2bb564244ab99853c9ae386e4f7298baf6dc0
The bug Talon spotted is still active, when you tick 'pay transaction fee' =.1 and send darksend only it still crashes. (curiously the instantX only with .1 of transaction fee seems to work now) Problem signature: Problem Event Name: AppHangB1 Application Name: darkcoin.exe Application Version: 0.11.1.18 Application Timestamp: 52cf3800 Hang Signature: a338 Hang Type: 0 Locale ID: 2057 Additional Hang Signature 1: a338d8bd53c652672a93d732701b0700 Additional Hang Signature 2: e9d2 Additional Hang Signature 3: e9d240c4226dde87c0ba7734432a7c19 Additional Hang Signature 4: a338 Additional Hang Signature 5: a338d8bd53c652672a93d732701b0700 Additional Hang Signature 6: e9d2 Additional Hang Signature 7: e9d240c4226dde87c0ba7734432a7c19
I was checking my MN and I noticed alot of this directly in the console. this is a snippet of the debug log where it started. This was a version behind the head.. so I updated darkcoind. maybe ignore this unless it happens again.
reversed (sent it back to sender) my earlier received InstantX transaction after it reached 6 POW confirmations, went through fine : Status: 5/confirmed (verified via instantx), broadcast through 28 node(s) Date: 9-2-2015 23:47 To: Test 1 yAS9wHH4wGPRGfaASLXi1y9ddUWaTFxYn8 Debit: -49.8999 tDRK Transaction fee: -0.01 tDRK Net amount: -49.9099 tDRK Transaction ID: 2ef3fae5935fd581094767ec67ec3d31a040e29fdbc7a2057fc007ec0a824f0e-000
eduffield How does the reconverge work? Does it add a centralization aspect to things? Just trying to get down to the nitty gritty.
Wow Evan!! First time had 100% and you're trying to fork it at same time. Had 11 locks out of 11 transmissions very close together
when you are resending a certain received InstantX input amount make sure it has the following : - 6 POW confirmations (can be checked through coin control, input amounts, list mode) - exclude 0.01 for the InstantX transaction fee so if for example you received 50 tDRK through InstantX and it confirmed POW 6x you will need to select through coin control 49.99 if you want to resend that exact same input amount with InstantX as it needs to add that 0.01 fee as well.
Feature request: include the InstantX (if selected) fee into the fee calculation on the "Send" page. It's a bit annoying when you copy the amount _after_ fee into the "Amount" field and get the "...total exceeds your balance..." popup when the InstantX fee is added.
afraid not.. here you find the most recent update : https://darkcointalk.org/threads/v0-11-1-x-instantx-release-testing.3826/page-51#post-41365 edit : oh wait, it does have the most current update on page 1. Didnt notice that .. very handy
How did ya test it, I mean, did you have to cause a fork to test? Be back in a bit to see answer, LOL (always taking off...)
As I understand things, it's seeing it's older version cached masternode start from the network. Which is usually a temporary condition. Meaning it'll usually go offline after a while. After a protocol bump, you should issue masternode stop/start to make sure your latest version is in the network cache. Make sure you send the start from a matching protocol version local wallet! No. The coins can stay put. You only need issue a masternode start to updated remotes from an updated local wallet. Adding back my 2M/s -- was offline for a bit.
So I still have a weird issue where when I send an InstantX transaction it will show up as spendable/available on the receiving wallet after one confirmation, but in the transaction details, it will say "InstantX verification in progress, 13 of 20 signatures" and then eventually say "InstantX verification failed" Why does it say it failed if it obviously worked?
This happens when dealing with very large amounts on 0.11.0.X on main net, too... I decided to take the low to no payments timeframe to remix some coins, sending the blobs around resulted in incorrect fee calculations. This bug may not be solely IX, like the other...
