RC4 Launch

Status
Not open for further replies.
just tried sending +/- 20 DRK with the 9.12.26, but didn't get a dialog to pay a transaction fee. Checking the block explorer it is sent with 0.00 fee. Is this correct or a small bug?
 
ruleland said:
just tried sending +/- 20 DRK with the 9.12.26, but didn't get a dialog to pay a transaction fee. Checking the block explorer it is sent with 0.00 fee. Is this correct or a small bug?
Click to expand...
Fees are calculated based on tx size, not amount sent.

eg. if you're sending 20DRK that's made up of a hundred smaller amounts it'll cost more than if it's made up of 20 smaller amounts... etc..
 
Are you reverting vertoe? It'll be a shame and a wrong message to send out but I understand why you need to do it
 
Am I really the only person experiencing massive CPU load and 30 second lag in the linux qt client? I'm using Xubuntu 14.04 and never had this issue before either on main-net or recently in test-net.
 
thelonecrouton said:
Am I really the only person experiencing massive CPU load and 30 second lag in the linux qt client? I'm using Xubuntu 14.04 and never had this issue before either on main-net or recently in test-net.
Click to expand...
It's generating transactions. Just leave the wallet alone a bit, it will settle down soon.
 
thelonecrouton said:
Am I really the only person experiencing massive CPU load and 30 second lag in the linux qt client? I'm using Xubuntu 14.04 and never had this issue before either on main-net or recently in test-net.
Click to expand...
1-5% for me, nothing unusual, no lags at all
 
crowning said:
Are you behind suchpool?
Click to expand...
No, but the operator is on IRC.

eduffield suchpool wont update until debug.log spam is removed from rc4 client.

Code: 
23:38:34  CryptoSiD | im updating suchpool right now  
23:38:35  CryptoSiD | to RC4  
23:38:41  vertoe | ok  
23:38:46  vertoe | that's what I want to hear!  
23:38:52  CryptoSiD | once we kick our next block  
23:38:56  CryptoSiD | since we'Re at 350%  
23:39:00  CryptoSiD | ha  
23:39:01  CryptoSiD | we just did  
23:39:12  CryptoSiD | but  
23:39:13  CryptoSiD | 2014-08-13 21:38:10 Misbehaving: 68.109.196.204:9999 (0 -> 1)  
23:39:13  CryptoSiD | 2014-08-13 21:38:10 ProcessMessage(dseep, 116 bytes) FAILED  
23:39:13  CryptoSiD | 2014-08-13 21:38:11 Misbehaving: 68.109.196.204:9999 (1 -> 2)  
23:39:13  CryptoSiD | 2014-08-13 21:38:11 ProcessMessage(dsee, 249 bytes) FAILED  
23:39:13  CryptoSiD | 2014-08-13 21:38:11 Misbehaving: 68.109.196.204:9999 (2 -> 3)  
23:39:14  CryptoSiD | 2014-08-13 21:38:11 ProcessMessage(dsee, 249 bytes) FAILED  
23:39:14  CryptoSiD | 2014-08-13 21:38:11 Misbehaving: 68.109.196.204:9999 (3 -> 4)  
23:39:14  CryptoSiD | 2014-08-13 21:38:11 ProcessMessage(dseep, 116 bytes) FAILED  
23:39:14  CryptoSiD | 2014-08-13 21:38:11 Misbehaving: 68.109.196.204:9999 (4 -> 5)  
23:39:15  CryptoSiD | 2014-08-13 21:38:11 ProcessMessage(dsee, 249 bytes) FAILED  
23:39:15  CryptoSiD | 2014-08-13 21:38:11 Misbehaving: 68.109.196.204:9999 (5 -> 6)  
23:39:16  CryptoSiD | 2014-08-13 21:38:11 ProcessMessage(dseep, 116 bytes) FAILED  
23:39:20  vertoe | at least one major pool updating is enough for me.  
23:39:39  CryptoSiD | im not sure i trust this  
23:39:42  CryptoSiD | to update the pool with it  
23:39:49  CryptoSiD | why the fuck are we getting all those error  
23:39:52  CryptoSiD | in debug.log  
23:40:01  CryptoSiD | 2014-08-13 21:39:08 ProcessMessage(dseep, 116 bytes) FAILED  
23:40:01  CryptoSiD | 2014-08-13 21:39:08 ProcessMessage(dseep, 116 bytes) FAILED  
23:40:01  CryptoSiD | 2014-08-13 21:39:10 ProcessMessage(dseep, 116 bytes) FAILED  
23:40:06  CryptoSiD | this is flooding the debug.log  
23:40:21  CryptoSiD | im not updating till its fixed  
23:41:16  elberethzone | CryptoSiD: probably an old node  
23:42:11  CryptoSiD | ive been saying this here everyday  
23:42:16  CryptoSiD | since thr rc4 beta is out  
23:42:24  CryptoSiD | it need to be fixed  
23:42:45  CryptoSiD | i won't update suchpool cause i dont trust this error flooding debug.log  
23:43:35  CryptoSiD | can seomeone report this on DCT  
23:43:37  CryptoSiD | ProcessMessage(dseep, 116 bytes) FAILED  
23:43:58  CryptoSiD | the debug.log is getting this line from 3 to 10 time every second.
 
vertoe said:
It's generating transactions. Just leave the wallet alone a bit, it will settle down soon.
Click to expand...
Hmmm, been an hour now and this is on an i5 @ 2.6GHz, no rocketship but it's not exactly slow normally either. Just thought, would having an encrypted HDD slow things up? As I say though, never experienced this on testnet with <=v25.
 
thelonecrouton said:
Hmmm, been an hour now and this is on an i5 @ 2.6GHz, no rocketship but it's not exactly slow normally either. Just thought, would having an encrypted HDD slow things up? As I say though, never experienced this on testnet with <=v25.
Click to expand...

Checkout tail -f ~/.darcoin/debug.log
Is it doing stuff? Leave it alone.
Is it not doing anything/frozen? Kill and restart it.
 
thelonecrouton said:
Am I really the only person experiencing massive CPU load and 30 second lag in the linux qt client? I'm using Xubuntu 14.04 and never had this issue before either on main-net or recently in test-net.
Click to expand...
Nope. I spoke with Evan about it briefly. He is going to implement some optimizations to try and mitigate this moving forward. It should stop once the wallet is finished denominating.
 
eltito said:
Nope. I spoke with Evan about it briefly. He is going to implement some optimizations to try and mitigate this moving forward. It should stop once the wallet is finished denominating.
Click to expand...
Thanks eltito! And thanks Vertoe too, debug log shows it slowly but steadily generating keys, (among other things) - currently only up to about 350. :eek:
 
Evan and team! Well done! RC4 works fine so far ;) There is much to do with RC5 and other bugs which will occur. So my nod to all of you team! :)
 
I'm a bit late, but I got my masternodes up and running, thank you everyone!

P.S. I'm wondering how this works regarding masternodes. If you upgrade, and the block is found by a pool that hasn't upgraded yet, will you still receive the funds? Also, does the miner get to keep the 20% if he upgraded and the designated MN wasn't? (this would be excellent as it would encourage miners to update before the masternodes :tongue: - a nice trap :wink: )
 
TanteStefana said:
I'm a bit late, but I got my masternodes up and running, thank you everyone!

P.S. I'm wondering how this works regarding masternodes. If you upgrade, and the block is found by a pool that hasn't upgraded yet, will you still receive the funds? Also, does the miner get to keep the 20% if he upgraded and the designated MN wasn't? (this would be excellent as it would encourage miners to update before the masternodes :tongue: - a nice trap :wink: )
Click to expand...

As I understand it old pools pay old MNs and upgraded pools pay upgraded MNs.
 
TanteStefana said:
I'm a bit late, but I got my masternodes up and running, thank you everyone!

P.S. I'm wondering how this works regarding masternodes. If you upgrade, and the block is found by a pool that hasn't upgraded yet, will you still receive the funds? Also, does the miner get to keep the 20% if he upgraded and the designated MN wasn't? (this would be excellent as it would encourage miners to update before the masternodes :tongue: - a nice trap :wink: )
Click to expand...
RC4 pools pay RC4 MNs, RC3 pools pay RC3 MNs... I've already had an RC3 pool not pay me because my MNs are RC4, hopefully the major pools will update reasonably quickly... by the look of chaeplins page some RC3 MN got the payment instead.
 
Status
Not open for further replies.
Back
Top