Show Posts
|
Pages: [1] 2 3 »
|
We were a bit delayed in updating the SourceForge repo.
If you have any problems, uninstall the wallet, download the latest version and install it.
Any further problems should be resolved.
|
|
|
Thank you for your kind words. This has been a challenge that none have yet faced before. We wanted to take the time to get it right.
If you have any issue, please repull the repo.
We're making a slight cosmetic change to the wallets and they will be back online shortly.
The work is running and blocks are staking.
|
|
|
It looks like a bad pull of the repo.
Do a "git pull" and make sure you got everything.
|
|
|
New wallets have been provided for both Windows and Linux. https://sourceforge.net/projects/bitseedsofficialrepository/files/Please uninstall your old wallet before installing the new one. The previous blockchain files must be deleted. Retain your "wallet.dat" file as that will unlock your funds on the new blockchain. This project is a long term mission. Should the network have been tested such as this and had a larger user base, the results could have been catastrophic. The previous blockchain has been added to the repo for fungibility and posterity. Previous commits may be compiled and the blockchain reviewed by any interested party. 2,000,000BITS have been moved to 2 wallets from the BitSeeds Foundation custody amount for staking independently. Additional amounts may be moved for staking should it be required. We encourage supporters to please stake their coins.We cannot fully express our gratitude for your patience and understanding as we resolved this issue. We look forward to serving you and the mission of the Rainforest Foundation.
|
|
|
All wallets have been successfully repopulated and a few blocks were successfully staked using the Foundation wallet.
We'll be creating a distributable release in the morning.
Wow. The rich list sure looks completely different. That's the result of change addresses generated from the repopulation of the blockchain. We decided it was best to implement the solution as simply as possible.
|
|
|
All wallets have been successfully repopulated and a few blocks were successfully staked using the Foundation wallet.
We'll be creating a distributable release in the morning.
|
|
|
The new network has been created and the coins are aging to maturity.
We will be relaunching as soon as possible. Thank you for your patience.
|
|
|
So, what you're saying is you plan to release a new version of the wallet client that would disable proof of work and rely on only proof of stake from here onwards. And anyone who purchased or mined Bitseeds will still have their balance (and presumably would be able to receive any balances stuck on the pools)?
While I was looking forward to continuing mining in the future, I don't have a problem with any of the above if it gets things up and running again.
What about the 900K+ mined by the person/people who attacked the network? Looking at the rich list I have to assume they own most of the wallets in the top 10 aside from the Foundation's and one other one I recognize. Any other changes happening beyond switching to POS only? Thanks for the update.
You are essentially correct. We are not concerned about the 900k coins. Those individuals mined those coins at great expense. They earned them. While technically an "attack" as the blockchain was damaged, there is no evidence of malicious intent.
|
|
|
The mission of BitSeeds and the BitSeeds Foundation is to assist the Rainforest Foundation in their funding efforts. The coin was launched in a manner to allow for public participation in the mining process. A programmatic fix for the issues the blockchain now faces would take an unknown amount of time as the damage is truly unprecedented. We invite the public to download the blockchain and see it for themselves.
For every moment the blockchain isn't moving, the BitSeeds Foundation cannot carry out its mission. We feel very strongly that a solution must be created that not only gets the network operational in a short a time as possible, but is also fair and transparent to the community who has invested in the coin. We do not want to duplicate the problems that were experienced in the first 7 days of the network.
Towards that end, we would appreciate community feedback on the following solution.
We intend to create a new blockchain with the exact same number of coins that had been generated on the network as of block 76300. We are going to use the same blockchain parameters so old keys will still work. Coins will be sent to the exact same addresses on the new blockchain as currently exist on the old blockchain.
Consider it an effective hard fork.
While proof-of-work mining was originally desirable, the nature of the cryptocurrency space no longer affords an energy efficient manner of proof-of-work mining that is also secure enough for long term use. The space has simply evolved that quickly and that is a reality we must face. There is the possibility of a multipool in the future to allow miners to still participate distribution.
We are truly sorry such an unfortunate set of events occurred that created the position in which we now find ourselves. It is truly unprecedented in this space and the original blockchain will exist as a permanent testament to that fact. We will be happy to provide it to anyone in the future for their own research.
BitSeeds was created to cause a disruption. It already worked and we are just getting started.
Thank you for your patience and we welcome your feedback.
|
|
|
We would also ask that pool operators please shut down their pools and we thank them for their support.
We apologize for any inconvenience this may have caused.
|
|
|
We have removed the wallet downloads so we don't have to keep telling people to download a new one. The network had to hash block 76300, first. POS should confirm those blocks once the network returns to normal.
We have added checkpoints to the blockchain to protect it's integrity and are adding those to the wallets. Mac wallets will also be provided.
Oh, I see. You said "The new Windows wallet is available on the Source Forge repo" so figured it was there already. I'll keep an eye on the thread and Twitter so I can download it and stake. Thanks. And also thanks for providing a Mac wallet so I don't have to run Parallels while staking! We apologize for the confusion. We have edited the post so that others would not find themselves as confused.
|
|
|
We have removed the wallet downloads so we don't have to keep telling people to download a new one. The network had to hash block 76300, first. POS should confirm those blocks once the network returns to normal.
We have added checkpoints to the blockchain to protect it's integrity and are adding those to the wallets. Mac wallets will also be provided.
|
|
|
Nobody is being "scammed" out of their honest earnings.
The blockchain is fine.
It is several months ahead of schedule miners have profited more than they would have in the same amount of time had the attack not have happened.
This coin's economics are not designed for the BitSeeds Foundation or the Rainforest Foundation to profit from market dumps.
The mining was the for the public, not for us.
We simply wanted public participation and this is what the public decided to do to a coin launched on behalf of a charity.
If you think anyone involved with this project has access to 600THs you are quite mistaken.
|
|
|
A checkpoint has been added to the repo at block 76300 with the proper hash.
Bittrex has been informed and will be updating. New wallets are being compiled. Those who have downloaded a fork by intent of the attackers should please be patient as the new wallets will contain the proper chain.
Thank you for your continued patience.
|
|
|
We agree completely.
They may certainly keep the coins as we hope they will support the efforts of the Rainforest Foundation. We have made this very obvious so that there can be no confusion.
As to why this vandalism continues we shall let the community and traders invested in the coin decide.
|
|
|
A copy of the blockchain has been saved at block 76300.
We will wait until the attackers are finished and load the proper chain.
00000000000004c27a48e5820a6c74a2fe36cdc1aba41d5f54cf017c5984944f
Is the hash of the correct block 76300.
|
|
|
We have already been in contact with bitseed.org via DM. I would ask that you please not create controversy where none exists.
We have shown willingness to compromise as our wallet symbol "BITS" conflicts with an existing coin on the markets. We have agreed to be traded as "XSEED" as to not cause confusion.
There is nothing wrong with the codebase. It is very standard in the altmarket. It is very easily reviewed, as is the blockchain.
We did things way so everyone would have a voice. The BitSeeds blockchain will forever bear the tale of what transpired. We are looking forward to the continuation of our project and your continued support.
The rest is for karma.
|
|
|
We are now all in this together.
Karma is indeed a bitch.
|
|
|
[Edited post to avoid confusion]
The BitSeeds Foundation is going to begin staking the custody amount and shall move it to other wallets as necessary to protect the blockchain. They will then be reassembled and put away when no longer necessary.
That's what it's for.
|
|
|
A new update has been posted to the repo.
Proof of work will be disabled at block 76300.
Bittrex is compiling new wallets and the markets should be online shortly.
Pools are asked to update immediately.
New installable wallets are being built now and it will be posted when the SourceForge repository has been updated.
Please do not stake your coins until you download this update. We will post when it is available, which should be very shortly.
Thank you for your patience and continued support of the Rainforest Foundation and its mission.
|
|
|
|