📅 Original date posted:2011-12-15
🗒️ Summary of this message: HTTP is easier to set up than DNS for dynamically responding with addresses. Third-party hosted services are more likely to provide aliasing resolution. Additional functionality could be added during the pre-transaction exchange process.
📝 Original message:>> Just so we're clear, what is the need for HTTP at all?
>> A query for a string and an answer can all be handled via DNS.
> It is a lot easier to set up an HTTP server to dynamically respond
> with addresses than a DNS record.
Interesting that you bring up the effort factor.
The notion that every individual will want to run their own DNS or
HTTP based alias system to dispense transaction-specific bitcoin
addresses seems - on this basis - alone a little far fetched. Such a
system would provide very little added value at significant hassle to
the small subset of users who could be bothered setting up such a
scheme. Also, remember that most people in the world don't even know
what DNS is, nor do they have the capacity or motivation to set up a
program on a web server for what amounts to minor ongoing time savings
and some vanity thrills.
To my mind, it is far more likely that third party hosted services
(such as providers of hosted wallet, conventional currency holding and
exchange services) will provide aliasing resolution, and that these
alias resolution services will operate on an alias at provider mechanism
(for example, IIBAN and its 'institution' codes @ ).
In addition, during the 'pre-transaction exchange' that the alias
resolution process essentially represents, additional value could be
added by these types of service providers by providing functionality
presently excluded from Bitcoin but relevant to real world financial
systems. For example this 'pre-transaction exchange' process might
include, in addition to alias resolution, transaction metadata
exchange (transaction description, invoice/order number, taxation
information, schedules of fees and charges, pre-arranged currency
exchange rates if filling an payment for an amount quoted in another
(eg: conventional) currency, shipping terms, transaction reversal
(cancellation) terms, escrow terms, etc.)
Regards,
Walter Stanish
Payward Inc.
Walter Stanish [ARCHIVE] /
npub1w7…wj55c
2023-06-07 02:47:06
in reply to nevent1q…e3x4
Author Public Key
npub1w7tezshngplj3fd8r9twxv6zujrwaxq7v98q6t4rdhd0y7u2tfnsmwj55cSeen on
wss://relay.nostr.bandPublished at
2023-06-07 02:47:06Event JSON
{
"id": "750c94fdd1d3b2be79de19ee23146e39448b5e68c03b90c4c347f99d8b5fe2d0",
"pubkey": "77979142f3407f28a5a71956e33342e486ee981e614e0d2ea36ddaf27b8a5a67",
"created_at": 1686106026,
"kind": 1,
"tags": [
[
"e",
"f45e7ca88e6eb3dd1e645e8e3cbb476c5b24e8003cb71eebe205594bb2a4d152",
"",
"root"
],
[
"e",
"eb3dc7921fa84a39a3ab77db670b64b1b0f586ad1bd34855249a11985e39649b",
"",
"reply"
],
[
"p",
"2bf5127c73a113bf09a0766d9cd9f0ee9ff75b959ed881d65f2d036610ad4b16"
]
],
"content": "📅 Original date posted:2011-12-15\n🗒️ Summary of this message: HTTP is easier to set up than DNS for dynamically responding with addresses. Third-party hosted services are more likely to provide aliasing resolution. Additional functionality could be added during the pre-transaction exchange process.\n📝 Original message:\u003e\u003e Just so we're clear, what is the need for HTTP at all?\n\u003e\u003e A query for a string and an answer can all be handled via DNS.\n\n\u003e It is a lot easier to set up an HTTP server to dynamically respond\n\u003e with addresses than a DNS record.\n\nInteresting that you bring up the effort factor.\n\nThe notion that every individual will want to run their own DNS or\nHTTP based alias system to dispense transaction-specific bitcoin\naddresses seems - on this basis - alone a little far fetched. Such a\nsystem would provide very little added value at significant hassle to\nthe small subset of users who could be bothered setting up such a\nscheme. Also, remember that most people in the world don't even know\nwhat DNS is, nor do they have the capacity or motivation to set up a\nprogram on a web server for what amounts to minor ongoing time savings\nand some vanity thrills.\n\nTo my mind, it is far more likely that third party hosted services\n(such as providers of hosted wallet, conventional currency holding and\nexchange services) will provide aliasing resolution, and that these\nalias resolution services will operate on an alias at provider mechanism\n(for example, IIBAN and its 'institution' codes @ ).\n\nIn addition, during the 'pre-transaction exchange' that the alias\nresolution process essentially represents, additional value could be\nadded by these types of service providers by providing functionality\npresently excluded from Bitcoin but relevant to real world financial\nsystems. For example this 'pre-transaction exchange' process might\ninclude, in addition to alias resolution, transaction metadata\nexchange (transaction description, invoice/order number, taxation\ninformation, schedules of fees and charges, pre-arranged currency\nexchange rates if filling an payment for an amount quoted in another\n(eg: conventional) currency, shipping terms, transaction reversal\n(cancellation) terms, escrow terms, etc.)\n\nRegards,\nWalter Stanish\nPayward Inc.",
"sig": "9f6213ef67b945380c080205126a077d36e4035c137df179d71f181924c38c7d56608285cff3c2f0d48d3edd48aa63de49d475349fb20e851845b4c2ce39c5ad"
}