RanchiMall's Token and Smart Contract system
Its possible that a committee member provided the right triggers for x number of contract before going rogue. Removal of the committee member after going rogue should not affect the previous contract's results. * Transaction comparision with blocktime has been implement when creating committee list * Order of execution of addition and removal is opinionated now to maintain consistency. Addition will be first, removal will be later |
||
|---|---|---|
| .gitignore | ||
| config-example.py | ||
| convert_db.py | ||
| models.py | ||
| old_parsing.py | ||
| parser_function_definitions.py | ||
| parsing.py | ||
| planning.txt | ||
| README.md | ||
| requirements.txt | ||
| smart-contract-system-redesign.txt | ||
| statef_processing.py | ||
| test_db.py | ||
| test_rebuild.py | ||
| test_rollback_new.py | ||
| tracktokens_smartcontracts.py | ||
FLO Token & Smart Contract System
The python script scans the FLO Blockchain for Token and Smart Contract activity and creates/updates local SQLite databases accordingly.