fusecavator
Member
Offline
Activity: 117
Merit: 10
|
|
March 28, 2015, 10:20:59 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb If you're an honest user it won't hurt anything. The problem appears if you forge your own chain from a point(ignore other blocks from other people, and do not broadcast your blocks to the network until later on). When you do broadcast your own chain whichever chain is weighted higher will win and replace the other one. Under normal circumstances your own chain would always lose unless you have a massive portion of the coin supply, but with intentionally aged coins split accross many accounts you might actually succeed. This is on traditional pos network read here for pos2.0 mods http://blackcoin.co/blackcoin-pos-protocol-v2-whitepaper.pdfThe dev said in this post https://bitcointalk.org/index.php?topic=997356.msg10914889#msg10914889 that there is infinite coin age accumulation, which directly contradicts that paper which says the improved pos is no longer using coin age.
|
|
|
|
fonzerrellie
Legendary
Offline
Activity: 1190
Merit: 1000
Kaspa
|
|
March 28, 2015, 10:23:34 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb If you're an honest user it won't hurt anything. The problem appears if you forge your own chain from a point(ignore other blocks from other people, and do not broadcast your blocks to the network until later on). When you do broadcast your own chain whichever chain is weighted higher will win and replace the other one. Under normal circumstances your own chain would always lose unless you have a massive portion of the coin supply, but with intentionally aged coins split accross many accounts you might actually succeed. This is on traditional pos network read here for pos2.0 mods http://blackcoin.co/blackcoin-pos-protocol-v2-whitepaper.pdfwow thanks for explanation and I'll read that pdf when I get a chance. so it would only give them a small window to take advantage of their work and the more popular of a coin it is then the more peeps watching the blockchain and everything so the shorter time frame they'd be working with? and sounds like a lot of work and timing for something that might not even succeed?
|
#Expanse $EXP 500 transactions 4 .1 EXP 1st Clone of ETH WAVES
|
|
|
Litecoinkid
|
|
March 28, 2015, 10:24:03 PM |
|
Lol, on another note, one of us will take your "memories" off of your hands Because he's a pussy ha ha
|
|
|
|
shimlbit
Legendary
Offline
Activity: 1302
Merit: 1001
|
|
March 28, 2015, 10:24:26 PM |
|
trolls back...
and he cant edit his previous post but want to tell the dev what pos 2.0 is
just shut up u troll and go elsewhere.. nobody need ur comments here in the thread,,,just move on
|
|
|
|
jadefalke
Legendary
Offline
Activity: 1456
Merit: 1014
|
|
March 28, 2015, 10:25:28 PM |
|
done. are you happy now? reason i sold now is: you kept calling me names. and also the dev doesnt know what pos 2.0 is. it does not accumilate coin age like he says. in pos 2.0 coin age does not matter. and that is good. the problem is he doesnt know what it is. ok, so now your done, please move on and troll somewhere else. Thanks.
|
|
|
|
Kimowa
|
|
March 28, 2015, 10:26:13 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb your weight does not go up pos 2.0 your weight is your number of coins that are mature. why the dev doesnt know this? Dev says coin age indefinitely and they do it says in the paper and dev said it I think you misread what he say
|
|
|
|
Kimowa
|
|
March 28, 2015, 10:28:52 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb your weight does not go up pos 2.0 your weight is your number of coins that are mature. why the dev doesnt know this? Dev says coin age indefinitely and they do it says in the paper and dev said it I think you misread what he say well he doesnt know what he is talking about in pos 2.0 coin age does not affect chance of finding a block He didnt say that lol
|
|
|
|
Kimowa
|
|
March 28, 2015, 10:30:35 PM |
|
In order to mitigate the possibility of the pre-computation attack, the stake modifier will be changed at every modifier interval – to better obfuscate any calculations that would be made to pinpoint the time for the next proof-of-stake.~ Read please http://blackcoin.co/blackcoin-pos-protocol-v2-whitepaper.pdf
|
|
|
|
crypto research
|
|
March 28, 2015, 10:31:19 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb your weight does not go up pos 2.0 your weight is your number of coins that are mature. why the dev doesnt know this? Dev says coin age indefinitely and they do it says in the paper and dev said it I think you misread what he say well he doesnt know what he is talking about in pos 2.0 coin age does not affect chance of finding a block How much coins you have for dump.
|
|
|
|
Hyperjacked
Legendary
Offline
Activity: 1610
Merit: 1119
It's all mathematics...!
|
|
March 28, 2015, 10:31:39 PM |
|
There is no max age in CRAVE...it works just like Blackcoin where your coin age will accumulate indefinitely. Isn't that a bad idea, since a small amount of coins can forge blocks easily and force a reorg if they've been kept offline accumulating age long enough, or is there some other way that is worked around? it's not like they'll build up a massive % return or anything being that it's a static 1 CRAVE per pos find... it's good that smaller wallets will be able to find blocks instead of only the massive holders finding them I'm not saying they'll build up a large return, I'm asking about it being easier to force a chain reorg for a double spend. A high amount of age accumulation can make it easier to find blocks, and splitting it across many addresses causes most of the age to still be preserved when a block is found. so they'll have better chances of getting multiple blocks in a day, I've gotten multiple blocks in a row on other coins but with much smaller net weights... it never seemed to hurt anything. I've heard about double spend lots but not sure I understand what it entails, it's obviously more than just getting multiple blocks... is it trying to send coins at the same time your getting blocks in a row or something? PS my wallet seems to be staying at a weight of 502... which is how many coins I have, does the age only increase every so often? I never owned any blackcoin so not sure how it's supposed to climb your weight does not go up pos 2.0 your weight is your number of coins that are mature. why the dev doesnt know this? Dev says coin age indefinitely and they do it says in the paper and dev said it I think you misread what he say well he doesnt know what he is talking about in pos 2.0 coin age does not affect chance of finding a block Your arrogance blinds you! This coin is the Shizzle and you know it...and by the way 28 btc is nothing compared to what your wallet would have looked like!
|
@Hyperjacked1 Twitter
|
|
|
fonzerrellie
Legendary
Offline
Activity: 1190
Merit: 1000
Kaspa
|
|
March 28, 2015, 10:31:46 PM |
|
not sure which I like best reg pos or pos 2.0... ended up not liking BITB cause thought it sucked that only big holders seemed to get any blocks. but I deff liked the static reward size
edit: I'll read that pdf to get a better understanding (overstanding)
|
#Expanse $EXP 500 transactions 4 .1 EXP 1st Clone of ETH WAVES
|
|
|
Litecoinkid
|
|
March 28, 2015, 10:38:42 PM |
|
Yeah go troll somewhere else mrz123,really no one cares,you're just a loooooser.....
|
|
|
|
Hyperjacked
Legendary
Offline
Activity: 1610
Merit: 1119
It's all mathematics...!
|
|
March 28, 2015, 10:42:46 PM |
|
Yeah go troll somewhere else mrz123,really no one cares,you're just a loooooser..... i am not trolling he should correct him self I understand...you want to buy back in!
|
@Hyperjacked1 Twitter
|
|
|
crypto research
|
|
March 28, 2015, 10:43:35 PM |
|
Yeah go troll somewhere else mrz123,really no one cares,you're just a loooooser..... i am not trolling he should correct him self I understand...you want to buy back in! It looks like he have 100k for dump.
|
|
|
|
Kimowa
|
|
March 28, 2015, 10:44:02 PM |
|
This is from Gavin Andersons blog and the dev already did the sigcache:
"I've been busy the last few weeks filling up my hard disk with copies of the main Bitcoin blockchain.
My goal is to prove that it is safe to raise the maximum block size from 1MB to at least 20MB, with the existing Bitcoin Core code (no fancy invertible bloom filters, no hyper-optimized-for-the Bitcoin-elliptic-curve verification code).
If the existing code can handle 20 megabyte blocks, then I'll argue we should schedule a hard fork to raise the block size. Ideally, we would never run into the maximum block size limit -- we would always have a situation like we do today, where miners decide how large or small to make their blocks, and people using the blockchain decide whether they're willing to pay miners transaction fees to include their transactions.
So I've been testing the existing code with much larger blocks -- 20MB and 200MB.
I could create artificial tests that fill up blocks with randomly generated transactions, but it would be much better to test with real-world transactions packaged into bigger blocks. I'm running a couple of full Bitcoin nodes, so I have 20 or so gigabytes of real-world transactions.
I just had to figure out how to repackage them into bigger blocks. After a couple of false starts over a couple of frustrating days (wouldn't it be nice if our ideas always worked perfectly the first time?), I came up with the following scheme:
First, I hacked the reference implementation and changed some constants related to the block size (MAX_BLOCK_SIZE, DEFAULT_BLOCK_MAX_SIZE, MAX_BLOCKFILE_SIZE). That part is easy.
The tricky bit is how to take transactions from the 1-MB and repackage them in bigger blocks. For most transactions, it is trivial, because ordinary transactions don't care what block they are in.
There are two exceptions:
1. Transactions that use the 'locktime' feature so they are not valid until a particular block height or date. I dealt with these by simply treating all transactions as 'final'.
2. There are special rules for 'coinbase' transactions: there can be only one coinbase transaction per block, it must be the first transaction, etc. My first couple of false starts went down the path of relaxing those rules, but I gave up that approach because I found myself changing more and more code. I think if I was 22 years old I probably would have just forged ahead, unwilling to let go of a couple of days of programming effort because "just one more change and it will probably all start to work..."
I wonder if old programmers throw away more code than young programmers. I bet we do.
Anyway, after a rethink I came up with a much cleaner solution for handling coinbase transactions from the real blockchain: I write them to a 'coinbasetx.dat' file which the hacked bitcoind reads at startup and stores in memory (there are only 73 megabytes of them). As blocks are added to the big-block chain, those coinbases are added to the "unspent transaction output set" so they are available to be spent (and I set the COINBASE_MATURITY constant to zero instead of 100, so they can be spent right away, in the same big block).
I wrote a tool ("gen_megablocks") that creates the coinbasetx.dat file and blk*.dat files that are valid-but-oversized, -regtest-mode blocks.
Those big blocks are then loaded into the bigger-block-capable bitcoind using the -loadblock command-line option, where they go through full transaction and block validation and indexing.
The end result is a fully-indexed blockchain with real transactions arranged into much larger blocks. I can import some of my main-chain wallet private keys and create transactions that spend them; those transactions are valid on both the hacked big-block chain and the main Bitcoin 1-MB blockchain (because ordinary transactions are completely independent of blocks).
So far, the results are very good-- the time to process a block scales up linearly with the size of the block, there are no hidden O(n^2) gotchas waiting to bite us. My desktop machine (a quad-core, 16GB-memory, "Late 2012" iMac) can easily keep up with a 20-MB-per-block blockchain, and could even keep up with a 200-MB-per-block chain if run with bigger -maxsigcachesize and -dbcache settings.
Today I'm generating alternate chains (I added an option to gen_megablocks to skip one or more transactions and their descendants); I'll be testing long and short blockchain re-orgs, measuring CPU time and memory usage. Once that is done I'll try syncing these 'megablock' chains across the internet and will measure real-world network bandwidth usage and time. And along the way I'll import a few keys and make sure the Bitcoin-Qt wallet works properly with big blocks (it should, it doesn't contain any code that cares about the block size).
Once all that is done, I will write up the results, write up a detailed specification for increasing the block size, and will start working on a patch (and lots more tests) to make it happen.
And I'm bracing myself for endless re-hashing of arguments about why a maximum block size tied to transaction volume or difficulty or exchange rate or total transaction fees or the phase of the moon would be better than some dumb, predictable formula...."
|
|
|
|
EmilioMann
Legendary
Offline
Activity: 2184
Merit: 1028
#mitandopelomundo
|
|
March 28, 2015, 10:45:07 PM |
|
dev please, create a new moderate thread against fud and troll
|
|
|
|
kondiomir
Legendary
Offline
Activity: 1568
Merit: 1000
Twitter @Acimirov
|
|
March 28, 2015, 10:46:13 PM |
|
Yeah. Good idea. Support that!
|
|
|
|
Hyperjacked
Legendary
Offline
Activity: 1610
Merit: 1119
It's all mathematics...!
|
|
March 28, 2015, 10:51:02 PM |
|
Maybe he will buy back some cheaper but I doubt most will sell into his scheme!
|
@Hyperjacked1 Twitter
|
|
|
EmilioMann
Legendary
Offline
Activity: 2184
Merit: 1028
#mitandopelomundo
|
|
March 28, 2015, 10:51:57 PM |
|
on a moderate thread is possible to use xsterminate, an app created by stealthcoin community to ban the trolls. Simply put the nick in the list and that troll never can write on thread again. https://bitcointalk.org/index.php?topic=850210.0
|
|
|
|
crypto research
|
|
March 28, 2015, 10:53:01 PM |
|
on a moderate thread is possible to use xsterminate, an app created by stealthcoin community to ban the trolls. Simply put the nick in the list and that troll never can write on the thread again. https://bitcointalk.org/index.php?topic=850210.0And price will go down like XST .
|
|
|
|
|