Closed xlc closed 3 years ago
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 200.0 DAI (200.0 USD @ $1.0/DAI) attached to it as part of the Centrality CENNZnet fund.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work has been started.
These users each claimed they can complete the work by 264 years, 8 months from now. Please review their action plans below:
1) coderwithattitude has started work.
I will tinker around with your blockchain and write up a post. 2) libtard has started work.
I will write the smart contract guide. 3) l-kh has started work.
I am trying to create a rust contract and then develop a front-end if I can.
Learn more on the Gitcoin Issue Details page.
@xlc, is this bounty still available ?
@Gungz yes^
@holygits I started working on the tutorial, just so I know, is this bounty still up for grabs ?
@Solexplorer yes
Background
Many application stacks interact with a backend server using a request- response pattern. smart-contracts, however, require a different architecture when used as an application backend.
One solution is to emit events from the contract after a request. A DApp then subscribes to new blocks and checks for any events from the contract, applying updates accordingly.
Write a blog post showing how to build a DApp with a smart-contract backend on a CENNZnet blockchain.
Expected Outcome
It should show the “emit event and watch” pattern. Additional bonus points for additional architectures or solutions.
Feel free to review our documentation and Github repos to get started: https://github.com/cennznet/spin2win/ https://github.com/cennznet/api.js
https://cennznetdocs.com/CENNZNet/index.md
It should use the CENNZnet js SDK in the DApp.
The smart-contract should compile and deploy on a CENNZnet blockchain.
Share the blog post and associated code for review