Noscription (Nostr + Inscription) is an experimental protocol for creating inscriptions for brc-20 alike tokens on Nostr for fun.

This is just a fun protocol that demonstrates how people can use Nostr to create chain-like data threads for inscribing something on it.

Unlike Bitcoin ordinals or BRC-20, data on Nostr relays are not guaranteed to be persisted forever (Ref: jb55’s Nostr post discussing how he reset the damus relay). Therefore, all Nostr events in this protocol are chained one by one, with each event tagging the previous event to ensure the sequence of events. Everyone, particularly Noscription holders, is strongly encouraged to keep a local copy of their events to ensure the persistence of their Noscriptions.

Idea

• There will be only one “genesis” event which declare the birth of Noscription Protocol
• There will be some deploy events, each deploy event declare the deployment of one kind of token on Noscription Protocol.
  • Each “deploy” event must tag the genesis event
• There will be some mint events, by announcing a valid mint event to Noscription relays, the sender can mint himself some tokens specified in the deploy event.
  • Each mint event must tag the previous one in a sequential order.
  • The first mint event, must tag the deploy event for that particular token.
  • There will be minting period definition in the deployment event. After such minting period expired, no new mint events will be considered as valid.
• There will be some transfer events, by announcing a valid transfer event to Noscription relays, the sender can move some token from his npub to another npub
  • The first transfer event can only be accepted after all tokens has been minted or the minting period has passed. It must tag the latest mint event.
  • For each transfer event, it is necessary to tag the previous transfer event that was announced.

Event Definition: Deploy

Event Content

{ 
  "p": "nrc-20",
  "op": "deploy",
  "tick": "noss",
  "max": "21000000000",
  "lim": "1000",
	"diff": "21",
	"seq": "arbitrum",
	"last_mint": "199999999"
}