I wanted to build a simple msgr system to have a chat on my itty-bitty-site: http://z1l3m.qr.ai without need for me or any user-side server. I came across a couple that claimed to do this, Shoutbox & an IRC portal.
Being these I have not gotten to work intuitively yet, I did come up with a simple QR based message relay system that mimics features of blockchain aka DLT technology. Features featured are as follows:
- Pseudonymity
- Blocks ( Event based blocks )
- Block Header
- Verifiable Trail ( previous hash include )
- Encrypted
- Double Encryption Capable
- Triple Encryption Capable
- Quick-Pairs ( 1-time Pairs )
- Layered Encrypted Chain ( each event can be self encrypted, same or different to the prev or next event/block )
- Variant Event Encryptions ( No one Encryption has to be the same per layered block/event )
- Independently Fork Capable
- Hidden/Unconnected Blocks ( Chain Fog )
- Digital Signatures Capable
As you can see I pulled technuiqes from Bitcoin-DLT as well as some Altcoin-DLTs.
What's in the Rules:
- Any server/cloud can be used to host faux-block
- Blocks are sent, printed or passed from one person to another
- In question of formats: if it can be linked it can be sent
What's a faux-block?
A block in this case is the message block/event (the actual message being sent), a faux-block is not the faux-face (final/sent QR) & is stored to have a link.
How does this have Pseudonymity?
By building faux accounts and/or use decentralized/anonymous cloud systems. Your message can be used for a 1-Time Verifiable Process. If nothing is saved/kept, your message doesn't have to appear in the next event but anyone you send the message to can fork it.
Now, the verfying block is called a Photon-block, in this case it's an audio file & an image of timestamp proof for the audio file.
--
Already, to my knowledge, there's been 3 forks, making 4 chains thusfar.
thanks for reading, look at the #HelpCHAIN to learn the verifying process.