Lots of traps when it comes to doing a web archive on bsv but reading this I'm going to add this to my notarizing service. I'm currently expanding the current service into a full merkle batched timestamp API that will include batch file notarizing and then web page notarizing (hashed time stamp paired with locally stored screenshots with a process for takedowns when it runs into malevolent / illegal links). Might be biting off more than I can chew but it would be huge if done right.
Post by 12UDCy…818c
Something like this?
USER
│
│ signs content
▼
POST
│
├── Content hash
├── User signature
└── Timestamp
│
▼
MERKLE BATCH
│
▼
BITCOIN
│
▼
MODERATION STATE
│
├── APPROVED
├── QUARANTINED
└── REVOKED
What the chain says
- Block
- 962 485
- Time
- 2026-08-15T22:22:29Z
- Signer
- 12UDCyC8EfHjW811M6xQNe5Mpv49Xc818c
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
12UDCyC8EfHjW811M6xQNe5Mpv49Xc818c UnverifiedReplies (4)
That's more or less the flow chart. Got it up and running at bsv.cx/.
Nice! Rather interesting, I like the way you worded things, that makes it a little easier to understand for those who are not so technically minded.
I'm building an asset ownership platform which has used similar logic in places, but still have a lot to do.
Nice job! Definitely well ahead of the game with that one! 😊
Thanks for checking it out. There's still wrinkles but it's coming together much faster than expected.
Honestly, really cool! Glad to see other things like this being built. These times are seriously great opportunities to be among the first to deliver working solutions that will before long likely become massively desired platforms.
Stick at it 💪