Hi y'all,
> In terms of achieving this level of binding within the Taro tree itself, I
> can think of three options:
The earlier BIP draft just sort of said "the commitment should be unique"
and hand waved away the exact algorithm used to verify this key property. I
thought about a few ways to
Hi Laolu,
> ignoring the rules leads to assets being burnt, but in most cases imo
that's a sufficient enough incentive to maintain and validate the relevant
set of witnesses
I agree it is sufficient, but only because using Bitcoin script without an
additional scripting language inside of Taro is
On Mon, Apr 11, 2022 at 11:21 AM Olaoluwa Osuntokun
wrote:
> Hi Bram,
>
> > The witnesses for transactions need to be put into Bitcoin transactions
> > even though the Bitcoin layer doesn't understand them
>
> Is this related to Ruben's comment about invalid state transitions
> (published in the
Hi Ruben,
> Also, the people that are responsible for the current shape of RGB aren't
> the people who originated the idea, so it would not be fair to the
> originators either (Peter Todd, Alekos Filini, Giacomo Zucco).
Sure I have no problems acknowledging them in the current BIP draft. Both
Hi Bram,
> The witnesses for transactions need to be put into Bitcoin transactions
> even though the Bitcoin layer doesn't understand them
Is this related to Ruben's comment about invalid state transitions
(published in the base chain) leading to burned assets? In the past, I've
considered using
From: Olaoluwa Osuntokun
>
> > Furthermore, the Taro script is not enforced by Bitcoin, meaning those
> who
> > control the Bitcoin script can always choose to ignore the Taro script
> and
> > destroy the Taro assets as a result.
>
> This is correct, as a result in most contexts, an incentive
Hi Laolu,
>happy to hear that someone was actually able to extract enough details
from the RGB devs/docs to be able to analyze it properly
Actually, even though I eventually puzzled everything together, this did
not go well for me either. There is a ton of documentation, but it's a maze
of
(this might be a double post as it ran into the size limit)
Hi Ruben,
Thanks! I don't really consider things final until we have a good set of
test
vectors in the final set, after which we'd start to transition the set of
documents beyond the draft state.
> Seeing as there's a large amount of
Hi Laolu,
Nice work. This is an interesting protocol, in my opinion.
Seeing as there's a large amount of overlap with RGB, a protocol which I
have examined quite extensively, I believe some of the issues I uncovered
in that project also apply here.
The biggest issue revolves around the
Good morning vjudeu,
> When I see more and more proposals like this, where things are commited to
> Taproot outputs, then I think we should start designing "miner-based
> commitments". If someone is going to make a Bitcoin transaction and add a
> commitment for zero cost, just by tweaking some
When I see more and more proposals like this, where things are commited to
Taproot outputs, then I think we should start designing "miner-based
commitments". If someone is going to make a Bitcoin transaction and add a
commitment for zero cost, just by tweaking some Taproot public key, then it
Hi y'all,
I'm excited to publicly publish a new protocol I've been working on over the
past few months: Taro. Taro is a Taproot Asset Representation Overlay which
allows the issuance of normal and also collectible assets on the main
Bitcoin
chain. Taro uses the Taproot script tree to commit extra
12 matches
Mail list logo
