Roadmap
Where Assign Onward development is planned to go. The goal is a system of blockchains created maintained and used by individuals and smaller entities. Rather than a massive centralized system embodying billions of trillions of dollars of value, each chain would be a more human scale from a few tens of thousands up to a few tens of millions of dollars, but the interoperable system of smaller blockchains has tremendous potential to serve a large number of people without a central point of control or failure.- First step is definition of a container format*This container format can be seen at work in the ProtoDev application.like strongly typed json, translatable to json to take advantage of json manipulation tools and increase visibility into the data but also translatable to a compact binary format for communication, storage, hashing and signatures. This same format should also support graphviz .dot visualization of containers and their data to facilitate visual understanding of the data structures and their interrelationships.
- Visual / user friendly tools*The ProtoDev is a somewhat visual/friendly application that assists in the development of Ⓐ protocols using bao formatted blocks.to build, save, restore and visualize data structures in the above formats are a stepping stone to the development of a protocol definition language.
- Define communication and storage protocols using the same container format. While it is possible to implement software that properly executes various actor roles in the developed protocols, I believe it will be much more powerful to define the protocols in a machine readable format and implement software which can interoperate across multiple*Protocol proliferation is already a problem in the broader cryptocurrency space. Assign Onward intends to tame this somewhat with standard protocol building blocks enabling the assembly of various functionality without having to "reinvent the wheel" as often as might otherwise be necessary. Hopefully, a small handful of dominant Ⓐ protocols emerge and become the standard (and interoperable) choices for most users.protocols.
- Given a protocol definition language, start implementing with the simplest of protocols with limited functionality (and limited applicability/value), building up from a well tested base with example/demo implementations to higher and higher functionality until the protocols are ready to start user simulation testing with adversarial user agents. A rough list of the DⒶ protocol development steps might be:
- Record / retrieve data - a super simple protocol
- Add requestor identity ( enables MQTT topic exchange use )
- Block chain storage / audit - first demo of blockchain functionality
- Share allocation / assignment - tracking something akin to value in/control of the chain
- Proof of stake multiple chain recorders - increased assurance for users, eliminiating single point of failure
- Share incentives for recorders - recruiting strangers to participate in the network
- Share expiry for inactivity - preventing loss of value/control due to abandonment/loss of secrets.
- Coin calculation for transactions and incentives - stabilizing relative value of coins as a percentage of active shares
- Offer and acceptance for share assignments - disallow assignment to non-actors, unwilling actors, etc.
- Record of offer expiry - concrete proof of contract expiration without execution, allowing free reassignment of offered shares in future contracts.
- Secure cross chain exchange - this is how Assign Onward conquers the world, from the ground up without massive concentration of value at the top
- Escrow assignment of shares for proof of stake - allowing shareholders to conditionally trust others to act on their behalf.
- Revocation of escrow assignment for proof of fault - trust, but verify - when a stranger defaults the escrowed shares control returns to the owner.
Assign Onward
4 October 2021
MIT License
Copyright (c) 2021 Assign Onward
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copyright (c) 2021 Assign Onward
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
2018 thinking
There's nothing really wrong with the 2018 roadmap, except that it skipped some foundational work that's envisioned in the 2021 thinking. The development tools will be somewhat different, and the protocol somewhat more flexible, but the basic elements are unchanged. The following items are in rough order of maturity.- Design
- Goals
- Architecture
- Functional requirements
- Implementation
- Recorded data format specifications
- Communication data format specifications
- Working application code
- Genesis Block Creator
- AOG¹ - Assign Onward Genesis block creator
- Asset Organizer, basic version
- AOS¹ - Assign Onward Seller - Asset Organizer for vendors
- AOE² - Assign Onward Explorer - Asset Organizer for consumers
- AOI² - Assign Onward Investor - Asset Organizer for market makers (a.k.a. AO-eye)
- Assignment Recording
- AOR¹ - Assign Onward Recorder - Records new authorized assignments on their chains
- AOV¹ - Assign Onward Validator - Independently validates AOR nodes*can be used as a source of invalidation, but not validation
- AON³ - Assign Onward Node - Distributed small world network cooperating/competing recorder
- AOL² - Assign Onward Licensing/Learning - Open records of educational achievement, professional licensing, complaints and resolutions.
- AOA² - Assign Onward Artist - records shares in artistic works of all kinds.
- Levels of Functionality (Test Assign Onward: the path)
- TⒶ¹ - Single recorder
- Offer and acceptance signed share assignments
- Recording tax (but no shares incentive for recorder)
- All checking done by the single recorder
- TⒶ²- Multiple chain transactions
- Protocol to guarantee a single transaction that involves multiple chains
- TⒶ³ - Multiple recorders
- Add share incentive for recorders
- Recorders check each other (maybe error catching rewards?)
- TⒶ⁴ - Underwriters
- Recognized share holders may provide underwriting to guarantee transaction
- Error checkers may claim rewards for validating the chain
- Error checkers may claim underwriting shares for exposing underwriting errors
- Testing
- Acceptance criteria for demonstration of functional requirements
- Automated demonstration of acceptance criteria
- System simulation
- Governance
- Process for revisions and extensions
- Interoperability with forks
Assign Onward
4 May 2018
MIT License
Copyright (c) 2018 Assign Onward
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copyright (c) 2018 Assign Onward
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.