I’m not a conformist to long-form verbosesness if not necessary - like writing a Phd level white paper or technical specification. Lord knows some of the subjects I’m floating require both the level of focus and attention to detail of a Phd trained practitioner.
I’m tightrope walking about 3 pretty seeming significant ideas right now - 2 less technical and challenging and 1 that demands all my focus to excel in. I have yet to give that 1 the proper level of attention that it deserves.
Here’re the 3:
- Analog businesses people can collaborate in sub-dao like orgs, possibly doing cross-promotion for IBC solutions or otherwise.
Currently looking into BIM 360 AR/VR solutions to satisfy this technical implementation so as not to be geo-fenced, but geo-centric.
Other places I’ve discussed this:
What is the general consensus in investing in businesses other than online blockchain apps? I think there is a huge opportunity to build DAO businesses that are more in the manual labor / robotic and automation sectors with a management structure.
- Construction
- Lawn Care
- Window Cleaning
- Mobility
- Farming
And the kinds of collabs that can be done with chains like Regen and other businesses in this sector.
…there are others.
There is obviously business development work and overhead associated, salaries for management team ect… with this strategy, but profit sharing and experimenting with this strategy would be an interesting social experiment. Part of the business development could include contacting businesses already established and investing in autonomous equipment with legal agreements on what the profit-sharing structure would look like.
- The ISO standardizations - self-explanatory
Other places I’ve discussed this.
ISO Standardization - Conversation - Cosmos Hub Forum - Comsos Improvements - It takes time to build a thorough understanding of any tech stack - especially when seeking to modify core functionality.
I have a lot to say on #3, but it’s not the low hanging fruit as a solo developer. I have a hunch about an implementation, but the design requirements for what I would deem satisfactory would be - quantum secure, privacy enabled, ephemeral and massively scalable. Filecoin has DAG Jose for encrypted data. Cosmos Blockchains are IPLD specified. I can paper napkin diagram the overall components - that’s a start.
Whose up for exploring paper napkin diagram ideas? The jist of it is a module that has a Kafka connector - all the ephemeral nodes are the source, and the sink - the place those ephemeral nodes write to - would ultimately be the root chain.
There could be an algorithmic ordering as a middleware between the injestion of all the ephemeral nodes and the output of all the blocks from all the data from all the nodes being ordered. After all those transactions are ordered submitting a transaction to the root chain preserves the process ordering of all the ephemeral nodes.
CometBFT API endpoints:
Endpoints that require arguments:
//localhost:26657/abci_info?
//localhost:26657/abci_query?path=_&data=_&height=_&prove=_
//localhost:26657/block?height=_
//localhost:26657/block_by_hash?hash=_
//localhost:26657/block_results?height=_
//localhost:26657/block_search?query=_&page=_&per_page=_&order_by=_
//localhost:26657/blockchain?minHeight=_&maxHeight=_
//localhost:26657/broadcast_evidence?evidence=_
//localhost:26657/broadcast_tx_async?tx=_
//localhost:26657/broadcast_tx_commit?tx=_
//localhost:26657/broadcast_tx_sync?tx=_
//localhost:26657/check_tx?tx=_
//localhost:26657/commit?height=_
//localhost:26657/consensus_params?height=_
//localhost:26657/consensus_state?
//localhost:26657/dump_consensus_state?
//localhost:26657/genesis?
//localhost:26657/genesis_chunked?chunk=_
//localhost:26657/header?height=_
//localhost:26657/header_by_hash?hash=_
//localhost:26657/health?
//localhost:26657/net_info?
//localhost:26657/num_unconfirmed_txs?
//localhost:26657/status?
//localhost:26657/subscribe?query=_
//localhost:26657/tx?hash=_&prove=_
//localhost:26657/tx_search?query=_&prove=_&page=_&per_page=_&order_by=_
//localhost:26657/unconfirmed_txs?limit=_
//localhost:26657/unsubscribe?query=_
//localhost:26657/unsubscribe_all?
//localhost:26657/validators?height=_&page=_&per_page=_
For those wondering how you checkpoint blocks from a layer two to a layer one the API above retrieves the blocks - every 50 or 100 or so, all those blocks are hashed, and we send the hash of all the combined data and checkpoint it into the chain. - from my understanding. I’ve never seen the function to accomplish this, but based on what I’ve read I would write a function that generally follows this process. A fraud proof would be a function that fetches those blocks, runs the same hash function and checks it against the hash of what’s been checkpointed into the chain. Again - I’ve never written a fraud proof function, but that’s how I would reason that process.
What Larry’s building could be the VM ephemeral nodes that spin up??? cwsoftware123
Having feedback from someone with Kafka expertise would be useful. I’m sure as a research subject those that have expertise in cosmos and tendermint, this particular usecase is an interesting approach and I suspect will require more fine grained details and research, but on the surface this seems very viable.