<unnamed>

Public Key

npub1xs2ujdur5f653rjudvugjgtsaths04mpgl86rtcnrw24w7us8hmszc4k9q

Profile Code

nprofile1qqsrg9wfx7p6ya2g3ewxkwyfy9cw4mc86as50nap4uf3h92h0wgrmacpz4mhxue69uhhyetvv9ujumn0wd68ytnwv46qz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mqlsv7jq

Publishing to

relay.nostr.net

relay.damus.io

nos.lol

Last Notes

2023-06-07 15:04:55 UTC

- reply

📅 Original date posted:2013-07-22
📝 Original message:+1 and thank you. I've prototyped a couple different Bitcoin projects that
would benefit from this.
I'm traveling with poor 'net so I haven't read the patches yet. I echo pull
request comments about using Accept and Accept-Encoding headers. Same for
an API version number in the URL.
It'd be helpful, eventually, to have APIs corresponding to Bitcoin addr and
version messages. Metadata about the network and the peer, respectively,
are valuable in my use cases.
Michael
On Jul 22, 2013 1:43 PM, "Jeff Garzik" <jgarzik at bitpay.com> wrote:
> URL: https://github.com/bitcoin/bitcoin/pull/2844
>
> Adding an HTTP REST API for bitcoind has been occasionally tossed
> about as a useful thing. Such an API would essentially provide a
> decentralized block explorer capability, enabling easy external access
> to transaction/address/block indices that we maintain.
>
> The first two implemented API calls are simple, returning a block or
> TX given a simple query string based on block hash, e.g.
>
> GET /rest/tx/TX-HASH
> or
> GET /rest/block/BLOCK-HASH
>
> This can be easily accessed via command line cURL/wget utilities.
> Output formats -- binary, hex or json -- may be selected via a
> "bitcoin-format" header.
>
> The general goal of the HTTP REST interface is to access
> unauthenticated, public blockchain information. There is no plan to
> add wallet interfacing/manipulation via this API.
>
> --
> Jeff Garzik
> Senior Software Engineer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> See everything from the browser to the database with AppDynamics
> Get end-to-end visibility with application monitoring from AppDynamics
> Isolate bottlenecks and diagnose root cause in seconds.
> Start your free trial of AppDynamics Pro today!
> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130722/2c0063e6/attachment.html>

2023-06-07 15:02:39 UTC

- reply

📅 Original date posted:2013-06-03
📝 Original message:On Mon, Jun 3, 2013 at 5:43 PM, Melvin Carvalho <melvincarvalho at gmail.com>wrote:
> Sorry if this is a stupid question, but why would someone want to
> sacrifice their bitcoins?
>
Good question. One reason is https://en.bitcoin.it/wiki/Fidelity_bonds
Cheers,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130603/2d82b7c7/attachment.html>

2023-06-07 15:02:33 UTC

- reply

📅 Original date posted:2013-05-31
📝 Original message:On Fri, May 31, 2013 at 5:56 AM, Rune Kjær Svendsen <runesvend at gmail.com>wrote:
> I have an application that wants to keep up with new blocks as they come
> in. For that I can use the -blocknotify option with bitcoind, which will
> execute my application for each new block.
>
> The problem is that my app isn't necessarily quick enough to finish its
> work before a new block comes in and the app is executed again.
>
In a similar circumstance, I changed my -blocknotify script to quickly
append necessary information to a queue and immediately exit. A separate
script runs at all times monitoring this queue for work and performs the
labor intensive calculations.
I hope that helps.
--
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130531/82acd521/attachment.html>