Topic: [ANN] BitBean is Now Bean Cash | First v3 POS | First 20MB Max Blocks | 7+ Yrs. - page 2. (Read 276130 times)

We will be building a bridge that connects all our 3 main platforms together, via "The Farm".
The Bridge will connect our Discord, Telegram and self-hosted https://live.beancash.org (Mattermost) platforms.

Anything new on beancash at all?

The Bean Cash Android App is available here:
https://www.beancash.org/downloads.html

Future versions of the Bean Cash Android Light Wallet will be published on the Google Playstore. A new version (v1.3.3) is being developed.

I apologize for my absence. Been dealing with a health issue among other difficulties. I hope to have several news of developments coming soon.  

YOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO!!! the price doubled today... what's going on?

The Bean Cash Online Generator allows you to create your own paper Bean Cash Wallets or Brain Key Wallets (using a Memorized Pass Phrase). These wallets allow you to transfer Bean Cash Peer to Peer (Person to Person). By transferring Bean Cash in person, person-to-person, your Bean Cash is Real Cash, private and there are no fees to use Your money when transferred person to person. An added benefit is these types of transactions are secure, anonymous and not traceable!

The Bean Cash Generator has recently been updated and is now using Compressed WIF (Wallet Import Format) by default for the Bean Cash Digital cards.

https://www.beancash.org/cash

If you would like to order Bean Cash Cards already printed and physically secured (with security seals and thermally sealed), send an inquiry for quantity, denomination and your address and we will get back to you with a quote:   [email protected]

If you run the new v1.3.2.1 and you are on the wrong chain, it will close. In that case, follow the instructions on the bottom of the page for getting and installing a SnapShot:  https://www.beancash.org/downloads.html

1.3.1 (or any older version before it) should not be used anymore (especially to sync the chain). Since we didn't have a majority upgrade to v1.3.1 in time (over 2 months notice was given), we stayed with the majority and followed the longer chain (up until August 2nd.) v1.3.1 started enforcing the new timedrift rules on July 13th., but there was no blocks violating the new rules until shortly after July 19th., when a block was created more than 10 minutes too early. Since at that time we still didn't have a majority of nodes upgraded, we had everyone stay on the long chain. By the beginning of August we had a majority of nodes that had updated to v1.3.1 and v1.3.2 (which started enforcement of the new time drift rules on August 2), since that time the majority of the network was now enforcing the new time drift rules and the majority of nodes stayed on the chain following the new rules. v1.3.2 not only started enforcement of the new rules, but also no longer synchronizes with old nodes (those running before v1.3.0.0). v1.3.2.1 reverts a change that was impacting network performance and introduces a new Proto version, which will lock in the protocol changes when the majority is running v1.3.2.1. Once we reach a majority running v1.3.2.1, v1.3.3 will be released, which will once deployed, eliminate the orphans being generated by the old nodes and complete the network upgrade