Uniscribe

$ init uniscribe launch > status: live inscribe here: uniscribe.app

$ uniscribe market > status: live > token: UNI20 > buy: enabled > list: enabled UNI20 market is now open. buy, list, transfer. uniscribe.app/market

$ uniscribe mint > UNI20 supply: complete > next module: loading > transfers: site only every swap wrote. market terminal opens next. transfer only through uniscribe.app/my otherwise it won’t be indexed.

@hua69806874 Working on the site now. We are adding transfers through the interface Transfers should go through the site so they index correctly

@uniscribe_eth what happen？

Before v4, swaps were endpoints. With hooks, swaps become triggers. UNI20 uses that trigger to mint inscriptions. This is the first experiment. uniscribe.app

6/ How to mint: Open the uniscribe.app Connect your wallet Click Mint Confirm one transaction Receive 1,000 UNI20 units after confirmation Just one swap-powered inscription

5/ UNI20 supports three core operations: DEPLOY — create a new inscription tick MINT — claim allocation from an existing tick TRANSFER — move inscription balances through hookData All enforced at the contract level

1/ Introducing UNI20 Inscriptions on Uniswap v4 hooks A new way to deploy, mint, and transfer inscription assets through unisat v4 swap hookData

@hanhsianghou Reload website

@uniscribe_eth ?

$ init uniscribe launch > status: live inscribe here: uniscribe.app

$ init uniscribe > protocol: Uniswap v4 hooks > standard: UNI-20 > input: hookData / JSON > output: inscription event > launch: soon