From: Aymeric Vitte <aymeric@peersm•com>
To: Andrew Poelstra <apoelstra@wpsoftware•net>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Robert Dickinson <robert.lee.dickinson@gmail•com>
Subject: Re: [bitcoin-dev] Ordinal Inscription Size Limits
Date: Sat, 28 Jan 2023 17:47:46 +0100 [thread overview]
Message-ID: <b00ac602-30d5-829e-664e-d18f0e4dd762@peersm.com> (raw)
In-Reply-To: <3e3acd36-44d7-6823-4eb6-69affe111204@peersm.com>
I saw the other posts, then storage in witness, no, ordinals no for now,
let's keep things simple and understandable
I forgot to mention that the proposals envision a "local bitcoin" (for a
metaverse for example) wich is a fork of Bitcoin code, but of course not
a fork of Bitcoin, and which of course does not store anything in the
main Bitcoin chain, but which remains compatible (tx format) and coins
between chains can be swapped
Maybe nobody care, but the idea is to put bitcoin into the party as an
alternative to this ethereum mess
Le 27/01/2023 à 16:43, Aymeric Vitte a écrit :
>
> Le 27/01/2023 à 14:21, Andrew Poelstra via bitcoin-dev a écrit :
>> if people were storing NFTs and other crap on the
>> chain, then the Bitcoin fee market would become entangled with random
>> pump&dump markets
> So you mean that Bitcoin is out for NFTs, Metaverse and "web3"?
>
> LN is good but I don't think it can really adapt to everything, what I
> proposed yesterday looks complementary
>
> I clearly dislike the current NFTs existing systems, and to make it
> short NFTs as a whole until recently, it depends on what people mean by
> "NFT", and I did dislike any solution based on OP_RETURN (shxtty stuff
> flooding bitcoin with stupid proofs of nothing)
>
> BUT I changed my mind, one can say that I am contradicting myself
> everywhere (links in the proposals), but no, explaining why in the proposals
>
> Note that in my proposals you don't need to "mint" the NFTs (using a
> third party but not a stupid ethereum/bitcoin like super sidechain) and
> that you can reference millions of them in one transaction (low value
> NFTs like loyalty programms, discount coupons) in that case of course
> the low value NFTs are centralized
>
> That's the future, Bitcoin being out of this does not look plausible,
> currently NOBODY envisions bitcoin or LN for a web3 system, so people
> here might destroy my proposals, then please do, but I find them quite
> good compared to whatever exist
>
>
>
--
Sophia-Antipolis, France
CV: https://www.peersm.com/CVAV.pdf
LinkedIn: https://fr.linkedin.com/in/aymeric-vitte-05855b26
GitHub : https://www.github.com/Ayms
A Universal Coin Swap system based on Bitcoin: https://gist.github.com/Ayms/029125db2583e1cf9c3209769eb2cdd7
A bitcoin NFT system: https://gist.github.com/Ayms/01dbfebf219965054b4a3beed1bfeba7
Move your coins by yourself (browser version): https://peersm.com/wallet
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.peersm.com
Peersm : http://www.peersm.com
next prev parent reply other threads:[~2023-01-28 16:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 12:44 Robert Dickinson
2023-01-27 12:58 ` rot13maxi
2023-01-28 10:58 ` alicexbt
2023-01-29 10:34 ` Robert Dickinson
2023-01-31 8:58 ` Erik Aronesty
2023-01-27 13:21 ` Andrew Poelstra
2023-01-27 15:43 ` Aymeric Vitte
2023-01-28 16:47 ` Aymeric Vitte [this message]
2023-01-28 4:26 ` Robert Dickinson
2023-12-29 12:27 ` Greg Tonoski
2023-12-29 19:01 ` Nagaev Boris
2023-12-30 9:58 ` Erik Aronesty
2024-01-01 13:33 ` Brad Morrison
2024-01-01 16:08 ` Erik Aronesty
2024-01-03 9:11 ` Brad Morrison
2024-01-03 13:05 ` Erik Aronesty
2023-02-03 19:56 ` Melvin Carvalho
2023-02-04 14:25 ` Kostas Karasavvas
2023-02-06 16:39 ` Erik Aronesty
2023-02-06 17:31 ` Claus Ehrenberg
2023-02-06 18:05 ` Erik Aronesty
2023-02-07 12:17 ` Aymeric Vitte
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=b00ac602-30d5-829e-664e-d18f0e4dd762@peersm.com \
--to=aymeric@peersm$(echo .)com \
--cc=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=robert.lee.dickinson@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