@everyone Announcing v0.9.2-3, NON-MANDATORY, FOR MAINNET -- CRITICAL FOR TESTNET USE This release has no mainnet changes.
New use cases live on testnet
- Ability to create new .veth VerusIDs that are priced in USDC, paid for using $100 woth of Bridge.VETH, and useful as both self-sovereign VerusIDs and also to define Ethereum mapped currencies for use on Verus, Ethereum, and PBaaS chains across the network. While this was previously in the protocol, we will shortly roll out the Etherum bridge update that will let everyone easily use it.
- Full support for defining mapped currencies and easily exporting any PBaaS currency as an ERC20 to Ethereum's Rinkeby testnet. Using mapped currencies, you can even create your own provable, auditable, mapped stable coins, collateralized 100% provably by the protocol, using any ERC20 currency on Ethereum, such as DAI, USDC, or any other currency at all. Either root VerusIDs or.veth IDs can be used to create Ethereum mapped currencies.
- Ethereum bridge website now recognizes and makes it easy to use all exported, ERC20 PBaaS currencies and all mapped currencies in the new user interface.
With v0.9.2-3, and the soon to be launched update to the ETH bridge, ready now and expected on testnet within the next couple days, you can now create .your own, self-sovereign, permanent name.veth identities, and map currencies to them. For example, MYCOIN.VETH could be mapped to USDC, creating a fully decentralized, provable, auditable, currency that can be sent back and forth from Ethereum's USDC to Verus or any PBaaS chain as MYCOIN.VETH. You can do the same with any currency on Etherum and any identity you control that is either a root or *.veth VerusID.
The rest of these release notes are the same as the prior release. Drop by pbaas-development to help get PBaaS ready for mainnet!