A brief announce for the upcoming update - it's expected to be launched in the next 12-36 hours:
- A referral and staking bonuses are calculated fully and solemnly on the blockchain, so no cheats or rug pulls are possible: all our contracts are immutable as they are deployed and the source code is open, so you can check them out and see for yourself what you're working with
- As a member of the ecosystem, you're no longer depend on the periodical earnings calculated data - you can initiate the calculation yourself as you need it whenever you need it. Speaking of the gas costs - only the part required for personal calculation is calculated, so no extra costs attached! This is achieved by implementing a hierarchical structure of the service contracts that are your digital ID and the deed keeper.
- Entering the ecosystem, you're authenticating using your TronLink key pair and for the first time the corresponding contract and NFT(see downstrings for details) is created for the representation of membership. You will be able to sell your ID via our fully-decentralized marketplace to anyone whenever you wish for the price in RCBC that is set by you.
- The NFT is created to bind the service contract to it, so all the referral subnet is attached with it, so as it's activity history - you're able to transfer all your profile to another person via our marketplace without any limits or implications. Why the free transfer is altered from the ERC-721 implementation? That sacrifice is made for the sake of security, because of stealing malware that is well-known around the web to steal people assets including NFT’s and also because of the nature of the controlled tokens like USDT or USDC that use to freeze the accounts from time to time as they wish. Also a third-party centralized markets are a big concern in a matter of decentralization. Our marketplace has no backend at all: it’s a PWA with an open source code and it’s assets stored inside the IPFS and the open source smart contract that has no external controls at all. And our basic token – the RCBC – is already deployed and it is also open source and without any controls in it. So this is the only way to be 100% ensured of the problems mathematically.
- The marketplace has it's own irreplaceable contract with the Single-Page Application on HTML5 and JavaScript, served via IPFS and capable of being a PWA - Progressive Web Application - you can use it as a website or natively install it as an application for your desktop or mobile device. An application is capable of sending you local notifications, so you will be notified about all the important events you need to know about in the real time. All the notifications are coming through your very local host you’re running the application on and you can – and we think you should – set up the local IPFS node and a small Tron node. Tutorials for it are on the way to be made right after the deployment. If you have questions about it – join our Discord or Telegram groups and ask us – we will be glad to help you! Using our marketplace you can sell any TRC-721 compliant token, but be warned that in this case there is a risk of the token’s own smart contract – all the other risks are covered and mitigated there.
- A single blockchain address can own one ID NFT+Profile pair, but you can sell your old one and create a new one as many times as you need. Using NFT operator approval mechanism you can flexible enable an external management for your profile for future integrations without any worries about your funds and assets: only an owner can sell the NFT token and all the earnings claimed in RCBC tokens are sent directly to the owner’s address, not the operators one. Yes, you can also utilize ERC-20 approval mechanism to allow spending of your RCBC tokens as well – it’s totally up to you and can be done only from the owner’s consent.
- Why the TRC-165 is not implemented in our RCBC token contract? Because it’s just a reference implementation for the TRC-20 interface with our custom add-ons for a decentralized token distribution that is not touching anything in TRC-20 logic. And also a code is open as well, so there’s no need to pollute the blockchain with an extra unneeded bytecode. Other contracts will have TRC-165 where it’s needed
- We will start publishing a copy of the source codes in a GitHub repository – just to make it convenient to have it in one place. However – it’s not canceling TronScan code publishing e.t.c. - it is done already and will be done further, it will be just a copy.
Log in or sign up for Devpost to join the conversation.