Happy new year everyone.
I would like to explain the current limitations in what we have now vs what I believe (imho) should be improved, and Id also like to get the community input on a few different ideas.
So first of all with the last 4 years of geopolitical activity, the fight for free speech and instability in the world, on the positive end it has initiated the impetus to write features that are freedom related (sharing files freely, communicating freely, social media features, videos, timelines, chain storage, chain linked storage etc). On the downside, this huge influx of new features is hard to get right the first time around (IE we are constantly trying to improve them to finally settle on one foundation that works for the users and ultimately provides a valuable service people are willing to pay for - not in the form of software or fees, but either as an embedded part of biblepay or as pay as you go etc). This is definitely true of our blockchain storage and video features, they were 'sort of cool' but just not really scalable or ready for public consumption. Ive been working in the background to make a more stable architecture in all these areas. A scalable connection to StorJ that would actually host data for biblepay but in a decentralized way, and then a front end service that would allow the user to see the data in the form of a video, a post or an attachment to a parent object.
One other area of interest that Oncoapop had mentioned are that NFTs are actually pretty weak in the sense that anyone can technically pull down the underlying image, and this is true as well for OpenSea and all the ERC-721 type NFTs; the NFT is really a succinct contract with a root TXID that can be sold user to user, but where the weakness is, is the inside package of that NFT is just metadata that lives on IPFS, and is malleable. A good example of this would be if someone sells an NFT that points to an IPFS share and then later the originator takes down the URL; the image would actually disappear. So this is an area where we can improve NFTs, if we spend some time making a thread about it and re-writing NFT 2.0 as a new spec (to make sure we cover all the bases), then we go at it and release NFT 2.0. I was thinking NFT 2.0 could include software keys (for buying copies of software with registration codes in it) as well. It could also point to an immutable file share rather than a malleable file share (something we can talk about in the ERP thread).
I plan on discussing a few ideas and then making a roadmap for 2024-2025 to keep us busy with releases.
So I have 3 primary ideas for 2024 and would like feedback on these:
1) A quantum resistant blockchain. Quantum computers are real, and now you can buy them for $5k from China (with 4 qubits). Its only a matter of time before a QC can crack a 256bit cryptokey. One possible area of growth for us is if we decided to release one of the first quantum resistant wallets. I was thinking one way we could accomplish this would be (for backwards compatibility sake, as I would not want anyone who holds BBP to lose it in the current form), is to release a feature where users are generally expected to move their primary BBP holdings (lets say the dormant amount) into a quantum resistant address. This address would have special characteristics where BBP could not be moved out of it in the memory pool unless it satisfies a 16384 bit key length (for a quantum computer that would make it almost impossible to break).
2) BBP ERP system. This ERP would be the system that allows us to finish the true BBP sidechain 2.0 that was started, but not what I would consider to be finished. The sidechain idea as is, provides a loosely coupled CockroachDB sidechain synced to BBP blocks and is basically "cool", but not entirely integrated as tightly as Ethereum is. I am thinking what we need is to rewrite that with 100% coupling, that makes it impossible to advance the sidechain without a strong and durable full node synchronized hash; what this gives us is unlimited sidechain storage for NFT2.0, video and makes it fully trustable (permissionless); it also gives us the ability for users to create new organizations where they grant permissions to other users to access Functions or Data objects - giving us the ability to roll out an ERP system.
3) Parent Control Apps for Kids. This type of entry would add an enhancement to the BBP core wallet where it becomes a parent control app (as long as the core wallet is running on each child PC). What this does is let the parents control how long a child is on the internet for, and then it restricts the internet for that child.
Let me know what areas sound the most exciting and areas we should create threads to talk about these features in detail.
