pull down to refresh

Is this a replacement to Liquid Network?
reply
No, it's just a different way to handle tokens.
reply
I wonder how all these "stablecoin" options on lightning will fit togther, will it need central points to swap value between one another, lets say I have galoy stablesats and want to pay a taro user, how is that going to work?
Are they all interoperable, just using LN liquidity to move the sat balance in the background? If not whats the point of having walled garden assets?
reply
Just looked through their code... It's about where RGB was 2 years ago, where all it could do was tokens. Now RGB is a fully client-side validated generalized smart contracts platform. Nowhere in the Taro repo are contracts mentioned, it's a naïve fixed function implementation.
reply
Is this for NFTs on bitcoin? Haven't read up on it yet. All I read is "minting".
reply
In theory you can mint NFTs as well (called unique assets), but the protocol isn't optimized for it. It's optimized for assets that can be used for payments, e.g. stablecoins.
reply
Taro enables centralized mints to issue tokens using taproot outputs.
You can have a taro asset for stables, stonks, gift cards, rewards points, shitcoins, and NFTs.
Soon, you'll be able to send taro assets over Lightning. The sending and receiving node must support the token being sent, however, in-between nodes just route Bitcoin. Only the endpoints of the route observe the token's price volatility against BTC. In this way, Bitcoin is the value layer for arbitrary asset transfers.
reply
I'm struggling to wrap my head around the impact of this.
Let's say Taro gets adopted and proceeds down the golden path. What happens then? Do we see ICOs of new assets on Taro, for example?
reply
It would be cool if current addresses using Taproot could be airdropped something for being an early adopter.
reply
lmao ngmi
reply
not as straight forward. to receive an asset, the recipient must create an address first specific to the requested asset. the asset is then sent to a new taproot output, not an existing one
reply