|
5
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEVA] NevaCoin | PoS 2.0 / PoW Hybrid | Blake2s PoW | NO Premine |
|
on: December 12, 2017, 03:18:23 PM
|
Wake up Krile. Block chain is again stacked. What are you going to do about it?
I do not understand why you can not find some permanent solution?
Right now, at what stage is your project?
The current plan is to make a swap. Starting a new chain on a newer codebase, same pow algo same reward structure. The plan is to make a snapshot of the current chain at a certain block height, and put those balances into the genesis block of the new chain. Some of the changes: 1. longer block time (at least 5 minutes, if not more) 2. better difficulty target algorithm 3. PoW forever, coin will remain pos/pow hybrid 3. maybe annon features, not sure about this yet. Why do this: 1. start fresh, leave old bugs behind 2. longer block time, less blocks, faster sync, less confilcts and spontaneus "mini" forks in the network 3. go to current bitcoin codebase, segwit and all the fancy stuff Everything will be announced with enough time in advance. Right now I am still looking for a co-developer to help out with the deployment of this idea. The ideal timing would be march 2018 for the two year anniversary of Nevacoin, but hard to say if everything will be tested enough by then. Do you like the idea? Feedback welcome  Krile, i like your ideas. But what will be coin cap, how many will be created once when you make it POW forever? Second i would suggest to lower number of POS blocks, something like 25% compared with 50% now. Better target algorithm is a must! The coin cap will be the same as now, 26 milion with halving. The halving will be extended if the block time will be raised. So from the current 7 years to maybe 10 years. Or maybe I will reconfigure the schedule so it stays at 7 years. Not sure about that part yet. All the coin monetary parameters will stay the same, except the block time and tartgeting and other technical stuff. I wil consider this suggestion about reducing the number of pos blocks, if that is even plausible. |
|
|
|
|
7
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEVA] NevaCoin | PoS 2.0 / PoW Hybrid | Blake2s PoW | NO Premine |
|
on: December 03, 2017, 05:00:45 PM
|
Wake up Krile. Block chain is again stacked. What are you going to do about it?
I do not understand why you can not find some permanent solution?
Right now, at what stage is your project?
The current plan is to make a swap. Starting a new chain on a newer codebase, same pow algo same reward structure. The plan is to make a snapshot of the current chain at a certain block height, and put those balances into the genesis block of the new chain. Some of the changes: 1. longer block time (at least 5 minutes, if not more) 2. better difficulty target algorithm 3. PoW forever, coin will remain pos/pow hybrid 3. maybe annon features, not sure about this yet. Why do this: 1. start fresh, leave old bugs behind 2. longer block time, less blocks, faster sync, less confilcts and spontaneus "mini" forks in the network 3. go to current bitcoin codebase, segwit and all the fancy stuff Everything will be announced with enough time in advance. Right now I am still looking for a co-developer to help out with the deployment of this idea. The ideal timing would be march 2018 for the two year anniversary of Nevacoin, but hard to say if everything will be tested enough by then. Do you like the idea? Feedback welcome |
|
|
|
|
12
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][NEVA] NevaCoin | PoS 2.0 / PoW Hybrid | Blake2s PoW | NO Premine |
|
on: October 19, 2017, 10:46:52 AM
|
Not good at all. Block chain is stacked due to big auto algorithm change pools. What is worse they are mining only in order to dump the coins for profit-BTC.
There must be some kind of protection for this kind of spikes and block chain halts.
Can we implement something like this: if no coin mined in one hour period create dummy-orphaned block and jump to lower difficulty?
I hope its only by accdent and not some kind of attack. The last few days this is really becoming a problem, before it would get stuck for max an hour or so. Worst case I will make a snapshot of the chain and start a new one on a newer codebase (eg bticoin 14.0) |
|
|
|
|
13
|
Alternate cryptocurrencies / Announcements (Altcoins) / Re: BATA BTA ◈ SCRYPT POW/POS HYBRID & MASTERNODES & PROFIT SHARE PLATFORM
|
on: September 26, 2017, 02:57:26 PM
|
I have never seen a PoW minable coin where the block hashes aren't actually the proof of work (a bunch of zeros in front of the hash) Why is bata designed this way? Just a general curiosity Hi here is an example of a raw block: { "hash": "2959d2161759004644c9bda9ac37507a29b67b7bb3580ba1bcc610c3fa8b11d9", "confirmations": 1, "size": 241, "height": 779555, "version": 4, "merkleroot": "954945425eb40dbb2fc3d2d6ddc87d92ba268dc341d0fe03e71e76246e8599a1", "tx": [ "954945425eb40dbb2fc3d2d6ddc87d92ba268dc341d0fe03e71e76246e8599a1" ], "time": 1506434691, "nonce": 2002999098, "bits": "1c02b746", "difficulty": 94.25787966, "chainwork": "00000000000000000000000000000000000000000000000000c0c4830ef0bc35", "previousblockhash": "48e9cfa2a689877d4985f63df903a6027c1c14c35ed02107473d72fc351b607c" } If you are referring to chain work then an explanation is available here: https://bitcoin.stackexchange.com/questions/26869/what-is-chainwork"The chainwork value is really just the total amount of work in the chain." I know about chain work, its the cumulative work on the chain. I was wondering about the block hash, which tells the work on the individual block. Why is it hashed this way in bata. Example a peercoin pow block: {
"hash": "0000000000000000ee2f9eeca90dd0708459b7e78de9c64d19bc3e73fd2d8e8a",
"size": 3790,
"height": 324835,
"version": 1,
"merkleroot": "e97bfe5e6c6d4fbf4acb8956ae0228dd6f2047b690b8245e128683ce8688dcb7",
"time": "2017-09-26 11:24:01 UTC",
"nonce": 2768994299,
"bits": "1902e43a",
"difficulty": 1485349089.4013,
"mint": 50.94,
"previousblockhash": "4235e040578bae46616f11daa644fd1cb485db7c6a5948f5e40608785aa4a6b8",
"nextblockhash": "00000000000000011b4841bb4aead702f2e266ba645b7484c3a239bf67101f3d",
"flags": "proof-of-work",
"proofhash": "0000000000000000ee2f9eeca90dd0708459b7e78de9c64d19bc3e73fd2d8e8a",
"entropybit": 0,
"modifier": "213b2338aec7bc5a",
"modifierchecksum": "4ba28af2",
} The proofhash is the same as the block hash. Again I am just curious, if there is a special reason for this design decision |
|
|
|
|
Show Posts
