SmilaZvia treechat·1mo
Replying to #f2328931
❤️ 0 Likes · ⚡ 0 Tips
{
  "txid": "018625034a5974ea16fb0edb57e0ac7463419814b4ef7578b98d129368be9cfa",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Register your assets? Can you explain that? ...and what is the benefit and ...what's the point of that?",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "SmilaZ",
  "channel": null,
  "parent_txid": "f2328931d02dbe2532fc3930052edc021cff96fae6a59a0fba0ea937ff5b4366",
  "ref_txid": null,
  "tags": null,
  "reply_count": 2,
  "like_count": 0,
  "timestamp": "2026-03-09T18:44:20.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "SmilaZ",
  "ui_display_name": "SmilaZ",
  "ui_handle": "SmilaZ",
  "ui_display_raw": "SmilaZ",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}
⬇️
Caseyvia treechat·1mo
❤️ 7 Likes · ⚡ 0 Tips
{
  "txid": "a925f634209bdbd875eaa12167d543158bfa811dbf82afd6bb4e96a2b44c10a0",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Indeed, sure! :-) \r\n\r\nSo, eventually we aim to be one of the main 'hosts' for self-sovereign/self-custodial asset ownership records. \r\n\r\nUltimately, you will be able to register Patents, Digital Assets or Content, Copyright/TradeMarks, etc.\r\n\r\nThe system allows 3 different Tiers of registration currently.\r\n\r\n1 - Basic registration (on-chain timestamp) with Canonicalisation of the file uploaded.\r\n2 - Self-attested backing (self-signature) to claim the registration is legitimate.\r\n3 - Third party attestation (Lawyer/External Party), etc.\r\n\r\nThe problem we have is that many of our assets are actually held/stored in various third party 'oversight' boards. Eventually, for true self-sovereignty, the access to those registration records should not be anywhere but in your own possession, for the same reason it's not a good idea to store large funds on Exchange Wallets (not your keys, not your coins).\r\n\r\nIf an attacker, corrupt-insider, or fraudulent company wanted to do so, they could alter/delete your 'records', and deny any attempts to counter anything that happened.\r\n\r\nThis way, you own the entire audit trail, the time-stamped data, proof that the file uploaded was the correct one you're presenting, along with us using 'duplicate protection', so another creator simply cannot register an asset if it already is registered on-chain with us. In the event that someone perhaps claims asset rights to your content, a flag is mentioned which will allow you to raise a dispute, or be notified that you've already uploaded that exact asset previously, and prevent you from spending unnecessary funds re-doing the process.\r\nPeerMark takes a lot of complex data from the asset files, not just on-chain timestamped data, but we create a (.PMRK) package file, which can be used to verify you own the asset.\r\n\r\nSo, let's say for example, you create a song, taken a photograph, or you're a videographer \u2014 You can register it as a standard asset which is encrypted to only be accessible by you, and choose to list it on our Marketplace. You can either outright sell the asset, where we automatically handle the entire asset ownership transfer process. The alternatives are: You can list it under 'Licensing', so other users can pay to use/have access to the asset for their own purposes for the licensing period term/agreement, and you're paid for it accordingly to whatever you wished to charge for the license.\r\n\r\nIt's a bit like a really hardened way of enforcing creator rights such as how the PRS/PPL handle music rights, but removes the middle-men skimming off the top. All funds go to the creator. \r\n\r\nYou can also simply use it for your own asset ownership records, and raise the PeerMark evidence when required if ever entering a legal dispute.\r\n\r\nWe're also reaching out to Real-World asset Partners for verification on assets such as Luxury Goods, and more.\r\n\r\nIt's quite complex behind the scenes, but it honestly has many, many different use-cases \u2014 including an easy way to store actual files on-chain for true censorship-free freedom. If any harmful content is ever posted, users can report it, where we will then review and revoke the 'media' display, so whilst the on-chain data will still exist, it won't be rendered/accessible via the 'Public Share Link' which is provided upon registration.\r\n\r\nExample: https://beta.peermark.online/media/47eb027a-c51d-4874-9506-6dc8dfb4605b\r\n\r\nThis isn't stored in any of our databases, it's directly taken from on-chain TX Payloads and re-built to be rendered in the browser. \r\n\r\nUltimately, it's an additional hardening layer for asset ownership/authorship, which can help many creators/founders/etc. provide real immutable proof of record, but made simple through easy-to-use UX instead of complex 'Blockchain TX Building' having to be done manually.\r\n\r\nPreviously, most people tended to just 'leave a message' in the OP_RETURN output field, but that's not really utilisable unless browsing Blockchain Explorers. PeerMark allows you to store complete files, asset data, metadata, manifest files, timestamps, and additional data all in the OP_RETURN field with the files unique hash, enabling a really good way to mitigate any fraudulent claims, disputes, or allow easy asset ownership transfer in the future.\r\n\r\nI.E. You could tie a verified partners certificate ID where you bought a Luxury Watch from, for example into the data payload. The partner issues a Certificate at the time of sale to verify you did purchase it, and that the item is legitimate, whilst the entire PeerMark logic combines all other records with that, and allows a fairly simple way to allow attestations, and references to other, external means which are also included in the time-stamped on-chain registration/package files.\r\n\r\nPossession is not ownership/authorship, so this is essentially a means to retain complete self-sovereignty, whilst making fraud a lot, lot more difficult to achieve. \r\n\r\n(Sorry, I hope that makes sense, lol!)",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "Casey",
  "channel": null,
  "parent_txid": "018625034a5974ea16fb0edb57e0ac7463419814b4ef7578b98d129368be9cfa",
  "ref_txid": null,
  "tags": null,
  "reply_count": 2,
  "like_count": 7,
  "timestamp": "2026-03-09T19:03:31.000Z",
  "media_url": null,
  "aip_verified": true,
  "has_access": true,
  "attachments": [],
  "ui_name": "Casey",
  "ui_display_name": "Casey",
  "ui_handle": "Casey",
  "ui_display_raw": "Casey",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}
Signed by14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGKAIP!

Replies (2)

Caseyvia treechat·1mo
Replying to #a925f634
❤️ 0 Likes · ⚡ 0 Tips
{
  "txid": "39779c3653c93b707a553674b22da5858759f8037e6a45843d314daa756bd167",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "For direct on-chain storage of files, PeerMark splits the file into chunks, the chunks are stored in different TX Outputs, or for larger files, in multiple different Transactions.\r\n\r\nAs a result, PeerMark takes note of which TXIDs are required to rebuild the file from the OP_RETURN Payload, and can reconstruct the TXIDs in the correct order in order to rebuild the file itself. \r\n\r\nNo database storage needed, no chance of alterations/deletion.\r\n\r\nJust a neat way to render actual content from on-chain TXs!",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "Casey",
  "channel": null,
  "parent_txid": "a925f634209bdbd875eaa12167d543158bfa811dbf82afd6bb4e96a2b44c10a0",
  "ref_txid": null,
  "tags": null,
  "reply_count": 0,
  "like_count": 0,
  "timestamp": "2026-03-09T19:29:03.000Z",
  "media_url": null,
  "aip_verified": true,
  "attachments": [],
  "ui_name": "Casey",
  "ui_display_name": "Casey",
  "ui_handle": "Casey",
  "ui_display_raw": "Casey",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}
Signed by14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGKAIP!
SmilaZvia treechat·1mo
Replying to #a925f634
❤️ 2 Likes · ⚡ 0 Tips
{
  "txid": "2cd8d8e6ac3d6e945d16b884873f854e37bd4986e83b57851113466fa7226ca9",
  "block_height": 0,
  "time": null,
  "app": "treechat",
  "type": "reply",
  "map_content": "Thank you. That does sound interesting.\ud83c\udf40 May this one take serious root and be sincerely real with us.\ud83d\ude4f Not like that FM thing for music (that I found your name on as a profiteer), which deleted my song-upload of the first hip hop uploaded on there (which I also promoted it as), and then suddenly itnwas gone, and instead they now pressented several hiphop songs replacing mine. And it was the Bitcoin Anthem on top of it all, as if they hated BSV,  while they were using it for their platform. So I'm guessing that you too must have had a disappointing experience with those dishonest people there. It's Time for the good stuff. \ud83e\udeb7",
  "media_type": "text/markdown",
  "filename": "|",
  "author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "display_name": "SmilaZ",
  "channel": null,
  "parent_txid": "a925f634209bdbd875eaa12167d543158bfa811dbf82afd6bb4e96a2b44c10a0",
  "ref_txid": null,
  "tags": null,
  "reply_count": 1,
  "like_count": 2,
  "timestamp": "2026-03-09T19:29:03.000Z",
  "media_url": null,
  "aip_verified": true,
  "attachments": [],
  "ui_name": "SmilaZ",
  "ui_display_name": "SmilaZ",
  "ui_handle": "SmilaZ",
  "ui_display_raw": "SmilaZ",
  "ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
  "ref_ui_name": "unknown",
  "ref_ui_signer": "unknown"
}
Signed by14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGKAIP!