š
Original date posted:2016-08-02
š Original message:> As said, Open Asset is not a draft proposal and is already used in the
wild since 2014. We can't easily modify the protocol by now for improving
it.
You can, however, provide a new OA2.0 protocol that improves upon these
issues, and assure that upgraded wallets maintain support for both
versions.
It seems like OA's stance has *always *been to focus on integration, rather
than fixing the core protocol and then, by virtue of having the largest
integration, saying things like "it's too late to turn back now". Colu
and Chromaway/EPOBC also have stuff "in the wild".
I would love to see an RFC-style standard "multiple-colored-coin-protocol"
written by reps from all of the major protocols and that meta-merges the
features of these implementations - in collaboration with feedback from
core developers that understand the direction the protocol will be taking
and the issues to avoid. HTTP/TCP/IP MCCP/BTC
As it stands, investors have to install multiple wallets to deal with these
varying implementations. Merging them into one "meta-specification"
fairly soon might be in the best interests of the community and of future
shareholders.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160802/f8abe85e/attachment.html>;
Erik Aronesty [ARCHIVE] /
npub1y2ā¦5taj0
2023-06-07 17:52:08
in reply to nevent1qā¦64jw
Author Public Key
npub1y22yec0znyzw8qndy5qn5c2wgejkj0k9zsqra7kvrd6cd6896z4qm5taj0Published at
2023-06-07 17:52:08Event JSON
{
"id": "29ad85e60688f021f7d2ec4b9d0000c83efb59b18efd1dded4cc7a04dfa11c39",
"pubkey": "22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa",
"created_at": 1686160328,
"kind": 1,
"tags": [
[
"e",
"0783d681e47ad95de85334a9475b6d99aaf4ff98031409a24b5b1988373a8ca0",
"",
"root"
],
[
"e",
"990d56b2fcdc8ba0653e509b0881db8215cb8afc51853d4009fcd4d0019da52e",
"",
"reply"
],
[
"p",
"bf0548dc0ad239e9e1e0bba3c969632ded402a68091cde1b21a0895e90bc9a57"
]
],
"content": "š
Original date posted:2016-08-02\nš Original message:\u003e As said, Open Asset is not a draft proposal and is already used in the\nwild since 2014. We can't easily modify the protocol by now for improving\nit.\n\nYou can, however, provide a new OA2.0 protocol that improves upon these\nissues, and assure that upgraded wallets maintain support for both\nversions.\n\nIt seems like OA's stance has *always *been to focus on integration, rather\nthan fixing the core protocol and then, by virtue of having the largest\nintegration, saying things like \"it's too late to turn back now\". Colu\nand Chromaway/EPOBC also have stuff \"in the wild\".\n\nI would love to see an RFC-style standard \"multiple-colored-coin-protocol\"\nwritten by reps from all of the major protocols and that meta-merges the\nfeatures of these implementations - in collaboration with feedback from\ncore developers that understand the direction the protocol will be taking\nand the issues to avoid. HTTP/TCP/IP MCCP/BTC\n\nAs it stands, investors have to install multiple wallets to deal with these\nvarying implementations. Merging them into one \"meta-specification\"\nfairly soon might be in the best interests of the community and of future\nshareholders.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160802/f8abe85e/attachment.html\u003e",
"sig": "26b2788848bcda8d04e16c41b201fc404679710ec7f02a4ee908d1c87485fe692d172c2a5f8e85ef755e2362b4032e421f110bd5b5ba809fbd7d2328ad973fa0"
}