Event JSON
{
"id": "8513dfa1dbf4c44f0e3b0f026e3cf787f2fea46aeea12df1e80f5c58c7e93b48",
"pubkey": "2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331",
"created_at": 1719749925,
"kind": 1,
"tags": [
[
"e",
"93b1f7cfdcb18ace429fb1a25654a89b33fa87db60def3b8dfb36ab0a6ad86e6",
"",
"root"
],
[
"e",
"3f67348d114c3d0f2df7ebaebbef7f6ad4c973456516781078901d9d5b0dffe1"
],
[
"e",
"b13413b757a50e442b8ddd912a6b3e93e64dcee6cf8840cad0efc40b4088b79a",
"",
"reply"
],
[
"p",
"2efaa715bbb46dd5be6b7da8d7700266d11674b913b8178addb5c2e63d987331"
],
[
"p",
"a15d810bc59bcc5a06ac05068436d71475c89e8a99cc97323cae6ed27c73197c"
],
[
"p",
"577de06dce160a0379163a4bb7b680be3e0a0e1c68de6e6ba8c01134b44064dd"
],
[
"r",
"https://media.urbit.org/whitepaper.pdf"
],
[
"r",
"https://vaporware.gitbook.io/vaporware/overview/overview#persistence-plan"
]
],
"content": "We don't use WASM, we use an entirely new computational model called PLAN and a new Lispy/Haskelly functional language called Sire. The core of our system is an SSI (solid state Interpreter), Kinode's is not. (We'll have a blog post with a frendlier definition of the SSI soon, but for now there is this whitepaper that introduced this concept to the world: https://media.urbit.org/whitepaper.pdf . Disclaimer though that we are not building on Urbit, it's just that the SSI is a general concept.)\nWe've got some explanation of PLAN here: https://vaporware.gitbook.io/vaporware/overview/overview#persistence-plan\n\nKinode's identity/networking layer requires blockhain integration. Our networking and identity are optional, freely-chosen by the user, and compatible with standard, blockchain-less cryptographic keypairs very much like Nostr. In fact, you'll be able to use your Nostr keys as identy in our system!\n\n",
"sig": "61ae3593f17958ce4f8969a46c7c8cb0a1ecf6668d5b0c44f3ac18956aaf8a7b850286d408a82a35b6a43675384eb0e277fd562b1a803210595440f1ec321527"
}