- 
                Notifications
    
You must be signed in to change notification settings  - Fork 8
 
Open
Description
@todo
-  
datdot-substrate#6[runtime] simultaneous challenges -  
substrate-epoch#4[runtime] Fix build -  
datdot-substrate#2Update README.md -  
datdot-substrate#10cleanup, pull upstream, fix build -  
datdot-substrate#14make custom types in json format - 1) grab Nina's js stuff, figure out what's not working, let y'all know so we can have our complete life cycle with the onchain and offchain stuff working at least on cli or as a glorified integration test.
 -  
datdot-substrate#13Unexpected epoch change -  
datdot-substrate#31Getting started link? -  
account_create()extrinsic for new users to submit a signed public key with a "micro proof of work" and get a unique user ID and a small amount of minted funds in return, so they can start using other chain features. -  make some sort of 
provider poolto track and manage available providers and match jobs to the best providers available based on plans service level agreements given by sponsors -  
datdot-substrate#23Updates/Bug fixes -  
datdot-substrate#20make attestations & encoding-hosting-challenge flows work -  
datdot-substrate#19Generate types automatically in js instead of maintaining a types.json file indefinitely. -  
datdot-substrate#17Merkle Tree Proof deep dive. -  
datdot-substrate#18Issues from running substrate & service - 2) finish datVerify api docs.
 - 3) fill out the unimplemented stuff that we've already thought through.
 -  rename 
registerUsertoregisterSeeder -  
datdot-substrate#15bit shuffleing -  
datdot-substrate#16make lab environment to reliably test substrate chain scenarios -  
datdot-substrate#11Basic Calls Flow -  
datdot-substrate#9[runtime] figure out testing framework for runtime -  
datdot-substrate#8[runtime/idea] take advantage of instantiable modules. -  
datdot-substrate#7[runtime] random chunk-range seeding and seeder size preferences -  
datdot-substrate#5[runtime] document/discuss runtime api -  
datdot-substrate#3[runtime] refactor datdot runtime modules into frame pallets -  
datdot-substrate#22changes to the chain to match mauve's logic (mvp) -  from the perspective of the chain, what is our electron app?
- is it the runtime?
 - is it like an off-chain worker?
 - are there option what it could be?
 
 
Metadata
Metadata
Assignees
Labels
No labels