馃搮 Original date posted:2015-11-16
馃摑 Original message:Not a native english speaker myself, so I may have missed some things...
Yes, sorry about the link. I guess you can point to #6230 . I can
rebase it if needed but I would close it again because I don't want to
have too many things from #6382 opened at the same time (is noisy and
worse for review). My plan was to not open it independently at least
until after #6907 (and actually after 0.12 assuming #6907 gets in by
0.12). But then I would maybe open a new one and reference the old one
rather than reopening #6230 (which tends to be confusing).
I'm not really sure what's the best answer here...but #6382 is
certainly going to need rebase and the link will be broken again.
Maybe one answer is to copy some text from #6230 or the commit and add
it directly to the BIP instead of referencing to that commit (which
will be, at least until #6907 is merged, a moving target).
On Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello <marcopon at gmail.com> wrote:
> Thanks for the comments! Now I fixed the typos (hope to have got them all,
> English isn't my first language), clarified the chain part a bit, and fixed
> the link. There probably is a better way to reference that source code part
> with the genesis blocks hashs, in a way that doesn't need to be changed,
> maybe...
>
> Now the main change would be to put in a proper BIP number! :)
>
> On Sun, Nov 15, 2015 at 12:42 PM, Jorge Tim贸n <jtimon at jtimon.cc> wrote:
>>
>> Thank you for incorporating the feedback, specifically thank you for
>> using the genesis block hash as the unique chain ID.
>>
>> I wen't through the BIP draft and left a few of comments, but I really
>> like its simplicity and focus. Good work!
>>
>> On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitcoin-dev
>> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> > Hi!
>> >
>> > To anyone that followed the discussion (from some time ago) about the
>> > proposed new URI for Blockchain references / exploration, I just wanted
>> > to
>> > point out that I have collected the feedback provided, reworked the
>> > text,
>> > put the BIP on GitHub and created a pull request:
>> >
>> > https://github.com/MarcoPon/bips/blob/master/bip-MarcoPon-01.mediawiki
>> > https://github.com/bitcoin/bips/pull/202
>> >
>> > The need for an URI for this come to mind again in the last days looking
>> > at
>> > Eternity Wall, which IMHO provide a use case that we will see more and
>> > more
>> > in the (near) future: http://eternitywall.it/
>> > Using that service, when you want to check for the proof that a specific
>> > message was written in the Blockchain, it let you choose from 5
>> > different
>> > explorer.
>> > Mycelium wallet recently added the option to select one of 15 block
>> > explorers.
>> > And there's the crypto_bot on reddit/r/bitcoin that detect reference to
>> > transaction an add a message with links to 7 different explorers.
>> >
>> > I think that's clearly something that's needed.
>> >
>> > Bye!
>> >
>> >
>> > On Sat, Aug 29, 2015 at 1:48 PM, Marco Pontello <marcopon at gmail.com>
>> > wrote:
>> >>
>> >> Hi!
>> >> My first post here, hope I'm following the right conventions.
>> >> I had this humble idea for a while, so I thought to go ahead and
>> >> propose
>> >> it.
>> >>
>> >> BIP: XX
>> >> Title: URI scheme for Blockchain exploration
>> >> Author: Marco Pontello
>> >> Status: Draft
>> >> Type: Standards Track
>> >> Created: 29 August 2015
>> >>
>> >> Abstract
>> >> ========
>> >> This BIP propose a simple URI scheme for looking up blocks,
>> >> transactions,
>> >> addresses on a Blockchain explorer.
>> >>
>> >> Motivation
>> >> ==========
>> >> The purpose of this URI scheme is to enable users to handle all the
>> >> requests for details about blocks, transactions, etc. with their
>> >> preferred
>> >> tool (being that a web service or a local application).
>> >>
>> >> Currently a Bitcoin client usually point to an arbitrary blockchain
>> >> explorer when the user look for the details of a transaction (es.
>> >> Bitcoin
>> >> Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.).
>> >> Other times resorting to cut&paste is needed.
>> >> The same happens with posts and messages that reference some particular
>> >> txs or blocks, if they provide links at all.
>> >>
>> >> Specification
>> >> =============
>> >> The URI follow this simple form:
>> >>
>> >> blockchain: <hash/string>
>> >>
>> >> Examples:
>> >>
>> >>
>> >>
>> >> blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198
>> >> blockchain:001949
>> >>
>> >>
>> >> blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a
>> >>
>> >> Rationale
>> >> =========
>> >> I thought about using some more complex scheme, or adding qualifiers to
>> >> distinguish blocks from txs, but in the end I think that keeping it
>> >> simple
>> >> should be practical enough. Blockchain explorers can apply the same
>> >> disambiguation rules they are already using to process the usual search
>> >> box.
>> >>
>> >> From the point of view of a wallet developer (or other tool that need
>> >> to
>> >> show any kind of Blockchain references), using this scheme mean that he
>> >> can simply make it a blockchain: link and be done with it, without
>> >> having
>> >> to worry about any specific Blockchain explorer or provide a means for
>> >> the
>> >> user to select one.
>> >>
>> >> Blockchain explorers in turn will simply offer to handle the
>> >> blockchain:
>> >> URI, the first time the user visit their website, or launch/install the
>> >> application, or even set themselves if there isn't already one.
>> >>
>> >> Users get the convenience of using always their preferred explorer,
>> >> which
>> >> can be especially handy on mobile devices, where juggling with
>> >> cut&paste
>> >> is far from ideal.
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Try the Online TrID File Identifier
>> > http://mark0.net/onlinetrid.aspx
>> >
>> > _______________________________________________
>> > bitcoin-dev mailing list
>> > bitcoin-dev at lists.linuxfoundation.org
>> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>> >
>
>
>
>
> --
> Try the Online TrID File Identifier
> http://mark0.net/onlinetrid.aspx
Jorge Tim贸n [ARCHIVE] /
npub1fx鈥l2d8
2023-06-07 17:44:59
in reply to nevent1q鈥g2e
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Seen on
wss://relay.noswhere.comPublished at
2023-06-07 17:44:59Event JSON
{
"id": "03036622aa5f9edeb52fe31165101e5dd427753e7eb6ad2ad63a1c079b1049ee",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686159899,
"kind": 1,
"tags": [
[
"e",
"1435883c3df6784c49f401921cbcbbd2e3d0743cfb054979b5d7a64835c624a3",
"",
"root"
],
[
"e",
"e6f55b2115bcee7d253342ff35cd3a9950ee854bf0e4165cc5dcee9962b292db",
"",
"reply"
],
[
"p",
"5407287b78a2060becfadcd1d33e3ebc59ea39863ac2da5309beed2d37a80186"
]
],
"content": "馃搮 Original date posted:2015-11-16\n馃摑 Original message:Not a native english speaker myself, so I may have missed some things...\n\nYes, sorry about the link. I guess you can point to #6230 . I can\nrebase it if needed but I would close it again because I don't want to\nhave too many things from #6382 opened at the same time (is noisy and\nworse for review). My plan was to not open it independently at least\nuntil after #6907 (and actually after 0.12 assuming #6907 gets in by\n0.12). But then I would maybe open a new one and reference the old one\nrather than reopening #6230 (which tends to be confusing).\nI'm not really sure what's the best answer here...but #6382 is\ncertainly going to need rebase and the link will be broken again.\nMaybe one answer is to copy some text from #6230 or the commit and add\nit directly to the BIP instead of referencing to that commit (which\nwill be, at least until #6907 is merged, a moving target).\n\nOn Mon, Nov 16, 2015 at 1:59 AM, Marco Pontello \u003cmarcopon at gmail.com\u003e wrote:\n\u003e Thanks for the comments! Now I fixed the typos (hope to have got them all,\n\u003e English isn't my first language), clarified the chain part a bit, and fixed\n\u003e the link. There probably is a better way to reference that source code part\n\u003e with the genesis blocks hashs, in a way that doesn't need to be changed,\n\u003e maybe...\n\u003e\n\u003e Now the main change would be to put in a proper BIP number! :)\n\u003e\n\u003e On Sun, Nov 15, 2015 at 12:42 PM, Jorge Tim贸n \u003cjtimon at jtimon.cc\u003e wrote:\n\u003e\u003e\n\u003e\u003e Thank you for incorporating the feedback, specifically thank you for\n\u003e\u003e using the genesis block hash as the unique chain ID.\n\u003e\u003e\n\u003e\u003e I wen't through the BIP draft and left a few of comments, but I really\n\u003e\u003e like its simplicity and focus. Good work!\n\u003e\u003e\n\u003e\u003e On Sun, Nov 15, 2015 at 3:14 AM, Marco Pontello via bitcoin-dev\n\u003e\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e \u003e Hi!\n\u003e\u003e \u003e\n\u003e\u003e \u003e To anyone that followed the discussion (from some time ago) about the\n\u003e\u003e \u003e proposed new URI for Blockchain references / exploration, I just wanted\n\u003e\u003e \u003e to\n\u003e\u003e \u003e point out that I have collected the feedback provided, reworked the\n\u003e\u003e \u003e text,\n\u003e\u003e \u003e put the BIP on GitHub and created a pull request:\n\u003e\u003e \u003e\n\u003e\u003e \u003e https://github.com/MarcoPon/bips/blob/master/bip-MarcoPon-01.mediawiki\n\u003e\u003e \u003e https://github.com/bitcoin/bips/pull/202\n\u003e\u003e \u003e\n\u003e\u003e \u003e The need for an URI for this come to mind again in the last days looking\n\u003e\u003e \u003e at\n\u003e\u003e \u003e Eternity Wall, which IMHO provide a use case that we will see more and\n\u003e\u003e \u003e more\n\u003e\u003e \u003e in the (near) future: http://eternitywall.it/\n\u003e\u003e \u003e Using that service, when you want to check for the proof that a specific\n\u003e\u003e \u003e message was written in the Blockchain, it let you choose from 5\n\u003e\u003e \u003e different\n\u003e\u003e \u003e explorer.\n\u003e\u003e \u003e Mycelium wallet recently added the option to select one of 15 block\n\u003e\u003e \u003e explorers.\n\u003e\u003e \u003e And there's the crypto_bot on reddit/r/bitcoin that detect reference to\n\u003e\u003e \u003e transaction an add a message with links to 7 different explorers.\n\u003e\u003e \u003e\n\u003e\u003e \u003e I think that's clearly something that's needed.\n\u003e\u003e \u003e\n\u003e\u003e \u003e Bye!\n\u003e\u003e \u003e\n\u003e\u003e \u003e\n\u003e\u003e \u003e On Sat, Aug 29, 2015 at 1:48 PM, Marco Pontello \u003cmarcopon at gmail.com\u003e\n\u003e\u003e \u003e wrote:\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Hi!\n\u003e\u003e \u003e\u003e My first post here, hope I'm following the right conventions.\n\u003e\u003e \u003e\u003e I had this humble idea for a while, so I thought to go ahead and\n\u003e\u003e \u003e\u003e propose\n\u003e\u003e \u003e\u003e it.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e BIP: XX\n\u003e\u003e \u003e\u003e Title: URI scheme for Blockchain exploration\n\u003e\u003e \u003e\u003e Author: Marco Pontello\n\u003e\u003e \u003e\u003e Status: Draft\n\u003e\u003e \u003e\u003e Type: Standards Track\n\u003e\u003e \u003e\u003e Created: 29 August 2015\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Abstract\n\u003e\u003e \u003e\u003e ========\n\u003e\u003e \u003e\u003e This BIP propose a simple URI scheme for looking up blocks,\n\u003e\u003e \u003e\u003e transactions,\n\u003e\u003e \u003e\u003e addresses on a Blockchain explorer.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Motivation\n\u003e\u003e \u003e\u003e ==========\n\u003e\u003e \u003e\u003e The purpose of this URI scheme is to enable users to handle all the\n\u003e\u003e \u003e\u003e requests for details about blocks, transactions, etc. with their\n\u003e\u003e \u003e\u003e preferred\n\u003e\u003e \u003e\u003e tool (being that a web service or a local application).\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Currently a Bitcoin client usually point to an arbitrary blockchain\n\u003e\u003e \u003e\u003e explorer when the user look for the details of a transaction (es.\n\u003e\u003e \u003e\u003e Bitcoin\n\u003e\u003e \u003e\u003e Wallet use BitEasy, Mycelium or Electrum use Blockchain.info, etc.).\n\u003e\u003e \u003e\u003e Other times resorting to cut\u0026paste is needed.\n\u003e\u003e \u003e\u003e The same happens with posts and messages that reference some particular\n\u003e\u003e \u003e\u003e txs or blocks, if they provide links at all.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Specification\n\u003e\u003e \u003e\u003e =============\n\u003e\u003e \u003e\u003e The URI follow this simple form:\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e blockchain: \u003chash/string\u003e\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Examples:\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e blockchain:00000000000000001003e880d500968d51157f210c632e08a652af3576600198\n\u003e\u003e \u003e\u003e blockchain:001949\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e blockchain:3b95a766d7a99b87188d6875c8484cb2b310b78459b7816d4dfc3f0f7e04281a\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Rationale\n\u003e\u003e \u003e\u003e =========\n\u003e\u003e \u003e\u003e I thought about using some more complex scheme, or adding qualifiers to\n\u003e\u003e \u003e\u003e distinguish blocks from txs, but in the end I think that keeping it\n\u003e\u003e \u003e\u003e simple\n\u003e\u003e \u003e\u003e should be practical enough. Blockchain explorers can apply the same\n\u003e\u003e \u003e\u003e disambiguation rules they are already using to process the usual search\n\u003e\u003e \u003e\u003e box.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e From the point of view of a wallet developer (or other tool that need\n\u003e\u003e \u003e\u003e to\n\u003e\u003e \u003e\u003e show any kind of Blockchain references), using this scheme mean that he\n\u003e\u003e \u003e\u003e can simply make it a blockchain: link and be done with it, without\n\u003e\u003e \u003e\u003e having\n\u003e\u003e \u003e\u003e to worry about any specific Blockchain explorer or provide a means for\n\u003e\u003e \u003e\u003e the\n\u003e\u003e \u003e\u003e user to select one.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Blockchain explorers in turn will simply offer to handle the\n\u003e\u003e \u003e\u003e blockchain:\n\u003e\u003e \u003e\u003e URI, the first time the user visit their website, or launch/install the\n\u003e\u003e \u003e\u003e application, or even set themselves if there isn't already one.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e Users get the convenience of using always their preferred explorer,\n\u003e\u003e \u003e\u003e which\n\u003e\u003e \u003e\u003e can be especially handy on mobile devices, where juggling with\n\u003e\u003e \u003e\u003e cut\u0026paste\n\u003e\u003e \u003e\u003e is far from ideal.\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\u003e\n\u003e\u003e \u003e\n\u003e\u003e \u003e\n\u003e\u003e \u003e\n\u003e\u003e \u003e --\n\u003e\u003e \u003e Try the Online TrID File Identifier\n\u003e\u003e \u003e http://mark0.net/onlinetrid.aspx\n\u003e\u003e \u003e\n\u003e\u003e \u003e _______________________________________________\n\u003e\u003e \u003e bitcoin-dev mailing list\n\u003e\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\u003e \u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e --\n\u003e Try the Online TrID File Identifier\n\u003e http://mark0.net/onlinetrid.aspx",
"sig": "3223e01ebd3f81fdf24a404bbed1450900d8213a11a9253ed7d8aa4abac834fa2a80e363ce7489385aae7aebcf8666e1d32b552207aee0937065ba8e1e64fc66"
}