From: Peter Todd <pete@petertodd•org>
To: Olaoluwa Osuntokun <laolu32@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot Assets on Mainnet: Announcing tapd v0.3.0-alpha
Date: Wed, 18 Oct 2023 22:02:42 +0000 [thread overview]
Message-ID: <ZTBWAgQUlC+lmJVO@petertodd.org> (raw)
In-Reply-To: <CAO3Pvs8758W6pPr0z40dvh+y4OB3jiQMfRE-tRq4vkc6bGWxEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Wed, Oct 18, 2023 at 01:20:03PM -0700, Olaoluwa Osuntokun via bitcoin-dev wrote:
> A technical specification for the Universe/Multiverse protocol can be found
> here in the BIP:
> https://github.com/Roasbeef/bips/blob/bip-tap-pr/bip-tap-universe.mediawiki.
>
> At a high level, a Universe server is used by clients to verify new asset
> issuance, archive off-chain transaction data, and transmit proof information
> for transfers. A Universe data structure is an authenticated merkle-sum
> sparse merkle tree that maps an `(outpoint, scriptKey)` tuple to proof data.
> A `scriptKey` is the protocol's version of the pkScript/scriptPubkey we all
> know and love today.
Looks like you're missing a citation to my scalable asset transfer work from
2017:
https://petertodd.org/2017/scalable-single-use-seal-asset-transfer
The key concepts in universes is very similar.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-10-18 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 20:20 Olaoluwa Osuntokun
2023-10-18 22:02 ` Peter Todd [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTBWAgQUlC+lmJVO@petertodd.org \
--to=pete@petertodd$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=laolu32@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox