Correct, you cannot do this with Bitcoin or derivatives without making it insecure. Neither Bitcoin or any other clones I have inspected have replaced the original mempool technology or surrounding communications sub-system. To answer your question though I have to ask:
What does "the most recent block gets replaced fairly often by accident" mean and why would this occur? Is this a bug in Bitcoin?
If I understand correctly, you are saying that the improvements in network propagation of messages will diminish the probability of forks occuring to a such a low number that using 1/confirmation is safe? If the Bitcoin system of reorganization is only a fix and forking is just an artifact caused by communication lags, then I think I would call the Bitcoin system kind of a hack... But Satoshi was one sly fellow, so I'm not subscribing to this view just yet. Perhaps there are deeper reasons why he made things as they are... In any case, glitches in network are sure to happen even if the p2p is incredibly fast. And what about malicious attack with a private chain? John also wrote this on the VNL forums: https://talk.vanillacoin.net/topic/142/version-0-2-8-beta-release/5
|
|
|
It seems that it's already implemented? I transferred some coins today and it appeared to complete after one transaction.
It can be implemented in just any coin by simply altering the number of required confirmations, but doing so you'll compromise the network security. This is how the Bitcoin dev guide addresses this issue: 1 confirmation: The transaction is included in the latest block and double-spend risk decreases dramatically. Transactions which pay sufficient transaction fees need 10 minutes on average to receive one confirmation. However, the most recent block gets replaced fairly often by accident, so a double spend is still a real possibility. How does VNL prevent the recent block being replaced by reorganization without forking the chain? John stated that he will make an official explanation regarding how it exactly works, meanwhile he posted this on a few days ago: http://pastebin.com/fxLUsnPxThing is, John isn't really the man to explain everything in the smallest detail, but he never failed us with the features. Let's wait a bit for his final words on this.
|
|
|
The PoW Will stop ? Please see the first section labeled "Notice" in the OP.
|
|
|
@traumschiff
Could you answer me, what will happen with coins from "testing blocks"?
No coins are being generated in POW currently, only POS is generating coins (0.7% yearly). POW will continue in approx. a month with the 88 block rewards.
|
|
|
The price is low and low Price should only matter for daytraders and for short-term investors. The development roadmap and John's usual surprise projects are far more complex than what 99% of the altcoin developers are capable of. The old bitcoin code is not capable of similar instant transactions (zero confirm transactions), you can't even use single confirm transactions on it securely. People don't seem to realise that this coin will be an ultimate financial transaction tool which has evolved over what the bitcoin code has to offer.
|
|
|
Important!
Around 70 blocks left to the pause in POW, please update your clients if you are not on version 0.2.8
|
|
|
John is going to post an explanation soon on how secure single confirmation transactions are possible on VNL. Since VNL's codebase is different to Bitcoins or Peercoins this could be made possible without risking doublespends or any security issue.
|
|
|
Staking is about to get crazy competitive does the 88 vnl per block can be earned by staking during pow pause ? No changes to the staking rewards, the low 0.7% staking reward will stay, staking was never meant to be the main reward/income source, but rather a bonus and a way to secure the network.
|
|
|
If its not for you DON'T invest , we are well aware of peoples thoughts on such projects, like i said you leap or you don't its up to you,
Two of our 3 man team are hero members on this very forum but due to possible conflicts in other areas of crypto we will not be releasing our ID until launch day.. Id, Wallet, Full roadmap
If you believe in the concept then by all means invest, if not thanks for looking and see you on the moon :p
They are hero members, but you won't tell who until the BTC is in. Not sure if you are serious saying things like these in the current alt situation where there are 2x the amount of scams than legit projects.
|
|
|
Are there any (recent) guides about FPGAs, raspberyy pi's, etc around that I could look at? Might be a fun project Don't buy an FPGA until John's finished. No FPGA miner has been released yet. Also, you don't need to use a raspberry pi. It's just an option. You can use any pc. I was looking into them regardless. To learn, not buy. If you google fpga + whirlpool you will find some articles discussing the matter. The Mojo v3 board seems to be the best suited for the task with a built in micro controller and a Spartan 6 chip. You can find similar from china for -30% cheaper, but they could be also less reliable. I'm going to wait for John to release software though since I'm not good at programming.
|
|
|
News 04/05Wallet version 0.2.7 released. Changes: - Clients and Peers now store their blockchain in separate disk locations.
- Lowered Proof-of-Stake interval for clients to 200 seconds.
- General Bug Fixes
Note: Your client will automatically re-download the blockchain to the proper location given your platform. Future releases will remove the old blockchain files. Original announcement: https://talk.vanillacoin.net/topic/141/version-0-2-7-beta-releaseDownload link: http://vanillacoin.net/wallets.php i'm running new released wallet, is it downloading full blockchain again? Yes, I just run it also and it is downloading the blockchain. It made a new Folder named AppData\Roaming\Vanillacoin\blockchain\peer where it is downloading the new blockchain. The future release will clean out the old blockchain files.
|
|
|
News 04/05Wallet version 0.2.7 released. Changes: - Clients and Peers now store their blockchain in separate disk locations.
- Lowered Proof-of-Stake interval for clients to 200 seconds.
- General Bug Fixes
Note: Your client will automatically re-download the blockchain to the proper location given your platform. Future releases will remove the old blockchain files. Original announcement: https://talk.vanillacoin.net/topic/141/version-0-2-7-beta-releaseDownload link: http://vanillacoin.net/wallets.php
|
|
|
I'm really excited what comes in the future regarding the MinerPP Project. Added the info the the ann with the official link. John will have an additional announcement soon.
Sorry for being late, had a long few days.
|
|
|
Added a timeline to above the news section with the "bigger" milestones.
|
|
|
News 28/04/2015
Updated the ANN, I hope that this will help finding information easier.
And that doesn't include what john-connor was talking about for this week? I have a feeling that I am going to wake up one day and find crazy growth here... He prefers no hype around his projects so I left that out. Updating as soon as I can. Info just gone out form John: https://twitter.com/john_a_connor/status/593014728751849472
|
|
|
News 28/04/2015
Updated the ANN, I hope that this will help finding information easier.
And that doesn't include what john-connor was talking about for this week? I have a feeling that I am going to wake up one day and find crazy growth here... He prefers no hype around his projects so I left that out. Updating as soon as I can.
|
|
|
News 27/04/2015For anyone whos missed it, here is the link to the official timeline of John: https://talk.vanillacoin.net/topic/118/4-month-timeline/2This shows the 4 month development plan (not listing his new project which he hinted at a few days ago). CoinPP (Coin++) Project has been finalised and the project source files are pushed to GitHub. To read more about the project please read the OP and https://talk.vanillacoin.net/topic/120/coinpp-coin-project/2. If you are a developer and need help in understanding/using the project please contact john-connor on #Vanillacoin @ freenode.
|
|
|
|