thelonecrouton
Legendary
 Offline
Activity: 966
Merit: 1000
|
 |
May 05, 2015, 11:48:59 PM |
|
BN: ./bitcredit-cli getblocktemplate
{
"capabilities" : [
"proposal"
],
"version" : 2,
"previousblockhash" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f20528eec90945de",
"transactions" : [
{
"data" : "01000000012b9240b37e5c8c90a50e0dfbec6987efa8ab31b3de20d235f15996a9e2a16acd000000006a4730440220420523672c9f7a9a63314d37653471c47b22b7402ac0f290bb3cf4328f31116a02206f011834bf8878e1243e99c0c46658a8740e8d69261166e0632a75a4f99a9c590121024a7356d0320252b060d74eb1ca9e31975ad91f74eac489cd9cbeafefd2e6d4abfeffffff0280969800000000001976a914c1b34a9f8703bf9804411d95158f5ffb19634dbb88ac1b155302000000001976a914ffa8ba199bc4ee5f0b7a7c4b08b9356ef217284b88aceca20100",
"hash" : "aa1b65620ea85de0471ad7de71bd7e6a45800a2ca41c782ede8f31a706fcbb31",
"depends" : [
],
"fee" : 225,
"sigops" : 2
}
],
"coinbaseaux" : {
"flags" : "062f503253482f"
},
"coinbasevalue" : 5000000225,
"longpollid" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f20528eec90945de107256",
"target" : "0000203691000000000000000000000000000000000000000000000000000000",
"mintime" : 1430858040,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 400000,
"sizelimit" : 400000,
"curtime" : 1430869452,
"bits" : "1e203691",
"height" : 107255,
"votes" : [
],
"payee" : "5xyD2QYoWoaKMVFLfmvuMs9J1jvWwgP6EY",
"payee_amount" : 1250000056,
"banknode_payments" : true,
"enforce_banknode_payments" : true
}
Local QT: 00:46:07 getblocktemplate
00:46:07 CreateNewBlock() : TestBlockValidity failed (code -1)
|
|
|
|
|
|
|
|
Transactions must be included in a block to be properly completed. When you send a transaction, it is broadcast to miners. Miners can then optionally include it in their next blocks. Miners will be more inclined to include your transaction if it has a higher transaction fee.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 12:38:19 AM |
|
00:46:07 CreateNewBlock() : TestBlockValidity failed (code -1)
How many BNs are you connected to? The block fails if there is no BN payment |
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 12:41:51 AM |
|
00:46:07 CreateNewBlock() : TestBlockValidity failed (code -1)
How many BNs are you connected to? The block fails if there is no BN payment 2, one of which is mine:
01:40:19 getpeerinfo
01:40:19
[
{
"id" : 4,
"addr" : "176.126.241.192:9999",
"addrlocal" : "213.120.38.175:35118",
"services" : "0000000000000003",
"lastsend" : 1430871959,
"lastrecv" : 1430871840,
"bytessent" : 2726,
"bytesrecv" : 10130,
"conntime" : 1430869438,
"pingtime" : 0.07126800,
"pingwait" : 859.70199300,
"version" : 70008,
"subver" : "/Minato:0.30.16.7/",
"inbound" : false,
"startingheight" : 107254,
"banscore" : 0,
"synced_headers" : 107254,
"synced_blocks" : 107254,
"inflight" : [
],
"whitelisted" : false
},
{
"id" : 6,
"addr" : "198.52.160.64:8877",
"addrlocal" : "213.120.38.175:57820",
"services" : "0000000000000003",
"lastsend" : 1430871881,
"lastrecv" : 1430871828,
"bytessent" : 2406,
"bytesrecv" : 8940,
"conntime" : 1430869959,
"pingtime" : 0.04992100,
"pingwait" : 938.62499300,
"version" : 70008,
"subver" : "/Minato:0.30.16.7/",
"inbound" : false,
"startingheight" : 107254,
"banscore" : 0,
"synced_headers" : 107254,
"synced_blocks" : 107254,
"inflight" : [
],
"whitelisted" : false
}
]
|
|
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 12:48:31 AM |
|
00:46:07 CreateNewBlock() : TestBlockValidity failed (code -1)
How many BNs are you connected to? The block fails if there is no BN payment 2, one of which is mine:
01:40:19 getpeerinfo
01:40:19
[
{
"id" : 4,
"addr" : "176.126.241.192:9999",
"addrlocal" : "213.120.38.175:35118",
"services" : "0000000000000003",
"lastsend" : 1430871959,
"lastrecv" : 1430871840,
"bytessent" : 2726,
"bytesrecv" : 10130,
"conntime" : 1430869438,
"pingtime" : 0.07126800,
"pingwait" : 859.70199300,
"version" : 70008,
"subver" : "/Minato:0.30.16.7/",
"inbound" : false,
"startingheight" : 107254,
"banscore" : 0,
"synced_headers" : 107254,
"synced_blocks" : 107254,
"inflight" : [
],
"whitelisted" : false
},
{
"id" : 6,
"addr" : "198.52.160.64:8877",
"addrlocal" : "213.120.38.175:57820",
"services" : "0000000000000003",
"lastsend" : 1430871881,
"lastrecv" : 1430871828,
"bytessent" : 2406,
"bytesrecv" : 8940,
"conntime" : 1430869959,
"pingtime" : 0.04992100,
"pingwait" : 938.62499300,
"version" : 70008,
"subver" : "/Minato:0.30.16.7/",
"inbound" : false,
"startingheight" : 107254,
"banscore" : 0,
"synced_headers" : 107254,
"synced_blocks" : 107254,
"inflight" : [
],
"whitelisted" : false
}
]
do "banknodes list" I think i've found the issue, it's simply that the block has a higher diff and contains transactions. NANs fix for the pool did not actually resolve the issue, as a result the block will pass only via solo-mining. This is made worse by the fact that the more efficient miners have not been updated, yvg's or NAN's. I've set my GPU's on the task, but it may take a while. |
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 12:59:38 AM |
|
Chain is moving again, hurrah! But banknode list is empty on my local QT client. Despite getpeerinfo showing it being connected to two of them.
|
|
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 01:04:00 AM |
|
Chain is moving again, hurrah! But banknode list is empty on my local QT client. Despite getpeerinfo showing it being connected to two of them.
I've noticed that, too many moving parts for me to keep an eye on them all at the same time. I'm looking at it now, but the chain is moving after i restarted the pool. this week looks like it will end in fire-fighting. |
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 01:24:20 AM |
|
Chain is moving again, hurrah! But banknode list is empty on my local QT client. Despite getpeerinfo showing it being connected to two of them.
I've noticed that, too many moving parts for me to keep an eye on them all at the same time. I'm looking at it now, but the chain is moving after i restarted the pool. this week looks like it will end in fire-fighting. Hey, it's no fun if it's easy.  I'm not having the sending problems others are reporting. Can send to/from my local and BN wallets just fine. Remember to uncheck the Darksend box in the Send screen... this should in future probably be unchecked by default, thought I'd submitted a pull for that but maybe not. |
|
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 01:34:57 AM |
|
I agree. Either way he has a way of doing things, and i have mine. Maybe we will find middle ground somewhere. After we resolve this minor fork , we will have a lot to discuss.
Allow me to quickly pen my thoughts here
1) Collateral via multi-chain tracking
2) Internal management Money vs Currency
3) Stock trading on the blockchain
4)Fixed money supply management and tracking
5) Multi-token/Colored-token system.
6) Direct Fiat rates (no BTC middleman)
I'll expand on the above as much as i can soon, but these are the chief conceptual issues in my mind. I think some of the concepts may require diagrams.
Let me start with the first
As you all know, P2PL is the first item on the table for banking, though any have asked the question how we will approach the idea of scamers running with funds. Because these concepts are always evolving, we were initially to rely on the huge investment it would take to gain trust. This however resulted in questions of barriers to entry for newcomers. We had to think deeper and be more innovative. As some of you have seen, if i want to get something done, i may rely on re-purposing existing solutions because their code is tried and tested.
I came up with the following solution that fast tracks some items i had ear-marked for later but solves today's problems:- Basically, you can use coins from another currency as collateral for a loan. I am going to begin work on a separate client that works with our chain but also tracks multiple other chains whose coins can be accepted as collateral. While we cannot support every coin out there we will likely support the top coins in the community as well as those chosen by popular demand. One of the pre-requisites will be that the coin used for collateral must be sufficiently liquid to allow immediate liquidation should there be an issue.
So at time of loan request and approval/denial, the value of your collateral is calculated and if the loan is approved, the system generates an escrow address and sends a tx request. The winning node, automatically sets up an escrow address and sends the address to both parties. It then waits for the funds to enter, then the loan is processed by confirmation message sent to BN.
The system is highly complicated and requires a lot of coding and security. TBH a lot of it is beyond my reach as a coder, i will need a ton of help and this will not be easy.
So i'll take some time and expand on the rest later, but i'd like to make another impetant announcement.
Since the scope of the project is nearly completely defined, i have come to the point where i see no way beyond getting outside help and funding. I am now actively pursuing registering as a company and getting a legal framework put forward, once this is done, I'm putting my face on this project.
Developer with not only a plan but a grasp of reality.  |
|
|
|
|
|
alganonim
|
|
May 06, 2015, 09:43:28 AM |
|
My both wallets (0.30.16.7c, BN & local) stuck at block 107289, is it normal, and no fees for a 8 hours ?
|
|
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 10:34:27 AM |
|
My both wallets (0.30.16.7c, BN & local) stuck at block 107289, is it normal, and no fees for a 8 hours ?
Same here. Something is definitely amiss. And I assume I'm not the only one for whom solo mining via the QT wallet is impossible right now, it just instantly crashes. I don't think the in-wallet miner has been updated to work with enforcement, last line in debug.log is ERROR: ConnectBlock() : no banknode payment ( required=1250000056)
and stdout on crash is terminate called after throwing an instance of 'std::runtime_error'
what(): CreateNewBlock() : TestBlockValidity failed
Aborted (core dumped)
Might be because the QT client can't see any Banknodes?  edit: bitcreditd can still mine it seems, so I'm using that. |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 11:56:10 AM
Last edit: May 06, 2015, 12:12:51 PM by bitcreditscc |
|
it's either the miners or the pool, this is the output i am getting form the pool:- 2015-05-06 11:54:11.680281 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:11.680453 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:11.680549 Target: 1b2bba5ff26a23000000000000000000000000000000000000000000000000
2015-05-06 11:54:11.683432 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:11.683543 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:11.683685 Target: 1b2bba5ff26a23000000000000000000000000000000000000000000000000
2015-05-06 11:54:12.075911 GOT SHARE! 5tEMroG8umWezhg9AZD3zRQR344aPiujPS 27e96a39 prev 18481c8a age 9.55s
2015-05-06 11:54:12.088496 New work for worker! Difficulty: 0.000000 Share difficulty: 0.000001 Total block value: 50.000002 BCR including 1 transactions
2015-05-06 11:54:12.114716 GOT SHARE! 5vvturZwfcR77vnETZURvXwLtQEWGmtCAH cac5bafa prev 18481c8a age 9.60s DEAD ON ARRIVAL
2015-05-06 11:54:12.473464 GOT SHARE! 5ysLXT3jmb66p7qytMFgbBQekX2192FjYK bb77ace7 prev d53ae93a age 0.38s
2015-05-06 11:54:13.290494 P2Pool: 4 shares in chain (88 verified/88 total) Peers: 1 (0 incoming)
2015-05-06 11:54:13.290625 Local: 1627H/s in last 1.3 minutes Local dead on arrival: ~31.3% (24-40%) Expected time to share: 0.9 seconds
2015-05-06 11:54:13.290693 Shares: 87 (53 orphan, 30 dead) Stale rate: ~95.4% (88-99%) Efficiency: ~8.0% (3-20%) Current payout: (0.0000)=0.0000 BCR
2015-05-06 11:54:13.290759 Pool: 44H/s Stale rate: 42.9% Expected time to block: 15.0 hours
2015-05-06 11:54:13.783478 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:13.783630 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:13.783695 Target: 1df75680feb65f000000000000000000000000000000000000000000000000
2015-05-06 11:54:13.791153 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:13.791297 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:13.791382 Target: 1df75680feb65f000000000000000000000000000000000000000000000000
2015-05-06 11:54:15.099984 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:15.100145 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:15.100240 Target: 1df75680feb65f000000000000000000000000000000000000000000000000
2015-05-06 11:54:15.100836 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:15.100935 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:15.101029 Target: 1df75680feb65f000000000000000000000000000000000000000000000000
2015-05-06 11:54:15.640068 GOT SHARE! 5tEMroG8umWezhg9AZD3zRQR344aPiujPS 57bb75c9 prev 6173e7bf age 3.14s
2015-05-06 11:54:16.292202 P2Pool: 5 shares in chain (89 verified/89 total) Peers: 1 (0 incoming)
2015-05-06 11:54:16.292337 Local: 1648H/s in last 1.3 minutes Local dead on arrival: ~31.4% (24-40%) Expected time to share: 0.9 seconds
2015-05-06 11:54:16.292391 Shares: 88 (49 orphan, 34 dead) Stale rate: ~94.3% (87-98%) Efficiency: ~10.2% (4-23%) Current payout: (0.0000)=0.0000 BCR
2015-05-06 11:54:16.292466 Pool: 614H/s Stale rate: 44.4% Expected time to block: 1.1 hours
2015-05-06 11:54:16.341480 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:16.341663 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:16.341755 Target: 1ef4fee96309cc000000000000000000000000000000000000000000000000
2015-05-06 11:54:16.347113 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:16.347283 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:16.347384 Target: 1ef4fee96309cc000000000000000000000000000000000000000000000000
2015-05-06 11:54:18.112740 Worker 6E4ggFg78uEJoHdwE4N9PH2CNhNZE4JWVu submitted share with hash > target:
2015-05-06 11:54:18.112915 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee4
2015-05-06 11:54:18.112981 Target: 1ef4fee96309cc000000000000000000000000000000000000000000000000
2015-05-06 11:54:18.114155 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:18.114268 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:18.114377 Target: 1ef4fee96309cc000000000000000000000000000000000000000000000000
2015-05-06 11:54:18.115295 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:18.115386 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:18.115448 Target: 1ef4fee96309cc000000000000000000000000000000000000000000000000
2015-05-06 11:54:18.209076 GOT SHARE! 5tST3vaooyoxY3KjtVrGTzfdNS8CV4GmXq bbbe05ff prev 57f97f79 age 2.53s
2015-05-06 11:54:18.221494 New work for worker! Difficulty: 0.000001 Share difficulty: 0.000001 Total block value: 50.000002 BCR including 1 transactions
2015-05-06 11:54:19.294014 P2Pool: 7 shares in chain (91 verified/91 total) Peers: 1 (0 incoming)
2015-05-06 11:54:19.294154 Local: 1666H/s in last 1.4 minutes Local dead on arrival: ~30.7% (23-39%) Expected time to share: 1.0 seconds
2015-05-06 11:54:19.294206 Shares: 89 (49 orphan, 34 dead) Stale rate: ~93.3% (86-97%) Efficiency: ~12.5% (5-26%) Current payout: (0.0000)=0.0000 BCR
2015-05-06 11:54:19.294289 Pool: 194H/s Stale rate: 46.2% Expected time to block: 3.5 hours
2015-05-06 11:54:19.752108 GOT SHARE! 68UhXgDodiPco7geua2GpW9SuQKMe7J29f c5475e7a prev 68ac1fe6 age 0.35s
2015-05-06 11:54:19.998840 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:19.998983 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:19.999043 Target: 1d3b25ae3e929d000000000000000000000000000000000000000000000000
2015-05-06 11:54:19.999567 Worker 5v9JksHMsEdhHAaHDtUxoNhB3juiXs6ucU submitted share with hash > target:
2015-05-06 11:54:19.999637 Hash: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffeee1
2015-05-06 11:54:19.999698 Target: 1d3b25ae3e929d000000000000000000000000000000000000000000000000
2015-05-06 11:54:20.244204 GOT SHARE! 5qN3ZasN345N5UoEVg2iZ4DtwA8YjyjJic 12f71308 prev c5475e7a age 0.48s
2015-05-06 11:54:20.314292 GOT SHARE! 6Bf2ZzjdK8h98YRjB5FGiyB9DCuFGZxnxN f7834adb prev c5475e7a age 0.53s DEAD ON ARRIVAL
debug:- 2015-05-06 11:58:52 CActiveBanknode::Dseep() - SendDarkSendElectionEntryPing vin = CTxIn(COutPoint(4beccdfc1e, 1), scriptSig=)
2015-05-06 11:58:56 peer=2792 using obsolete version 70007; disconnecting
2015-05-06 11:58:56 ProcessMessage(version, 104 bytes) FAILED peer=2792
2015-05-06 11:59:03 peer=2793 using obsolete version 70007; disconnecting
2015-05-06 11:59:03 ProcessMessage(version, 104 bytes) FAILED peer=2793
2015-05-06 11:59:12 peer=2794 using obsolete version 70007; disconnecting
2015-05-06 11:59:12 ProcessMessage(version, 104 bytes) FAILED peer=2794
2015-05-06 11:59:31 peer=2795 using obsolete version 70007; disconnecting
2015-05-06 11:59:31 ProcessMessage(version, 104 bytes) FAILED peer=2795
2015-05-06 11:59:52 CActiveBanknode::Dseep() - SendDarkSendElectionEntryPing vin = CTxIn(COutPoint(4beccdfc1e, 1), scriptSig=)
2015-05-06 11:59:59 peer=2796 using obsolete version 70007; disconnecting
2015-05-06 11:59:59 ProcessMessage(version, 104 bytes) FAILED peer=2796
2015-05-06 12:00:08 connect() to 198.52.200.60:8877 failed after select(): Connection refused (111)
2015-05-06 12:00:20 CDarkSendPool::UpdateState() == 3 | 3
2015-05-06 12:00:20 peer=2797 using obsolete version 70007; disconnecting
2015-05-06 12:00:20 ProcessMessage(version, 104 bytes) FAILED peer=2797
seems there are still stragglers on the old code. but their clients are rejected immediately. |
|
|
|
doesntmatter
Newbie
Offline
Activity: 39
Merit: 0
|
|
May 06, 2015, 05:04:11 PM |
|
litemode disables all banknode activity! so with qt on litemode it can't mine... i can mine... someone with wallet that says up to date, and can be mined on send me ip, user and pass.... i will mine next block to get myself back up to date.... so i can keep the network up!!!
|
|
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 06:47:12 PM |
|
my analysis is complete and my initial views are correct. Here's the quickie-
Problem
Our p2pool software seems to have trouble handling blocks that contain transactions. As a result it fails to solve those blocks, further, with the absolute enforcement of BN payments, I cut out those who were dodging the payments by using NAN's outdated miner.
Resolution
Everyone capable of solo mining, please help out. Also I a working on resolving the "litemode" issue and will return with a report in a few hours.
As i do not know python, i am asking someone else to look into why our pools fail to handle transactions.
|
|
|
|
thelonecrouton
Legendary
Offline
Activity: 966
Merit: 1000
|
|
May 06, 2015, 07:43:32 PM |
|
Block 107290 has arrived, after 17hrs59mins!  |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 08:04:15 PM |
|
Block 107290 has arrived, after 17hrs59mins! apparently solved by p2pool after numerous restarts. i'm scouring both the wallet code and p2pool rooting out any issues i can find, but it's slow work. thats almost a whole day with no blocks and that is unacceptable. |
|
|
|
|
bitcreditscc (OP)
|
|
May 06, 2015, 11:53:15 PM |
|
Does anyone have problems with the BN payments schedule? int64_t GetBanknodePayment(int nHeight, int64_t blockValue)
{
int64_t ret = blockValue/5; //20%
if(nHeight > 85000) ret += blockValue / 20; // 25.0%
if(nHeight > 85000+((1440*30)* 1)) ret += blockValue / 20; // 30.0%
if(nHeight > 85000+((1440*30)* 2)) ret += blockValue / 20; // 35.0%
if(nHeight > 85000+((1440*30)* 3)) ret += blockValue / 40; // 37.5%
if(nHeight > 85000+((1440*30)* 4)) ret += blockValue / 40; // 40.0%
if(nHeight > 85000+((1440*30)* 5)) ret += blockValue / 40; // 42.5%
if(nHeight > 85000+((1440*30)* 6)) ret += blockValue / 40; // 45.0%
if(nHeight > 85000+((1440*30)* 7)) ret += blockValue / 40; // 47.5%
if(nHeight > 85000+((1440*30)* 8)) ret += blockValue / 40; // 50.0%
if(nHeight > 85000+((1440*30)* 9)) ret += blockValue / 40; // 52.5%
if(nHeight > 85000+((1440*30)*10)) ret += blockValue / 40; // 55.0%
if(nHeight > 85000+((1440*30)*11)) ret += blockValue / 40; // 57.5%
if(nHeight > 85000+((1440*30)*12)) ret += blockValue / 40; // 60.0%
return ret;
} |
|
|
|
Bagdar13
Member
Offline
Activity: 115
Merit: 10
|
|
May 07, 2015, 12:21:49 AM |
|
Does anyone have problems with the BN payments schedule? int64_t GetBanknodePayment(int nHeight, int64_t blockValue)
{
int64_t ret = blockValue/5; //20%
if(nHeight > 85000) ret += blockValue / 20; // 25.0%
if(nHeight > 85000+((1440*30)* 1)) ret += blockValue / 20; // 30.0%
if(nHeight > 85000+((1440*30)* 2)) ret += blockValue / 20; // 35.0%
if(nHeight > 85000+((1440*30)* 3)) ret += blockValue / 40; // 37.5%
if(nHeight > 85000+((1440*30)* 4)) ret += blockValue / 40; // 40.0%
if(nHeight > 85000+((1440*30)* 5)) ret += blockValue / 40; // 42.5%
if(nHeight > 85000+((1440*30)* 6)) ret += blockValue / 40; // 45.0%
if(nHeight > 85000+((1440*30)* 7)) ret += blockValue / 40; // 47.5%
if(nHeight > 85000+((1440*30)* 8)) ret += blockValue / 40; // 50.0%
if(nHeight > 85000+((1440*30)* 9)) ret += blockValue / 40; // 52.5%
if(nHeight > 85000+((1440*30)*10)) ret += blockValue / 40; // 55.0%
if(nHeight > 85000+((1440*30)*11)) ret += blockValue / 40; // 57.5%
if(nHeight > 85000+((1440*30)*12)) ret += blockValue / 40; // 60.0%
return ret;
} So likely there are people who cannot translate that directly into time (me being one of them), based on current solving could you list (maybe a graph how that changes over time months/years etc) |
|
|
|
|
|
bitcreditscc (OP)
|
|
May 07, 2015, 01:31:19 AM
Last edit: May 07, 2015, 02:07:36 AM by bitcreditscc |
|
So likely there are people who cannot translate that directly into time (me being one of them), based on current solving could you list (maybe a graph how that changes over time months/years etc)
https://docs.google.com/spreadsheets/d/1_wC7z9eKTMtbtyEfsd20PfH8SdUs9wKMX3JqYTJZxpQ/edit?usp=sharingPersonally i thought this is very fair, but some people have raised concerns. I am actually concerned that 22.5% is too low and wanted to raise it to 40% to incentivize BN owners. |
|
|
|
Department of
Member
Offline
Activity: 102
Merit: 10
|
|
May 07, 2015, 03:06:42 AM |
|
Yeah, I feel like it at least needs to be on a scheduled increase, not remain a constant. And 40% would definitely be a lot more incentive... |
|
|
|
|
Mario241077
Legendary
Offline
Activity: 1302
Merit: 1000
ORB has a good chance to grow.
|
|
May 07, 2015, 05:53:49 AM |
|
bitcreditscc, any ideas why block 107254 has so far taken 1hr42mins? I tried to setgenerate true to hurry it on a bit but got a core dump.  The pools have like 4-5 kh/s. at diff 3k, that should be solved in like 30 seconds ...i think its not on a high diff block so something else is up, as time proceeds i am sure it will illuminate itself. Also, it seems that the new wallet has fixed the syncing issue of yesterday so that's one down. can you post your getblocktemplate? Unfortunately, I still can not send! Any ideas? 07:52:55  getblocktemplate 07:52:55  CreateNewBlock() : TestBlockValidity failed (code -1) |
|
|
|
|
