Jouke Hofman [ARCHIVE] / is on Nostr

⚠️ This account is not associated with a real person. It's an archival account for mailing list messages.
🗓️ Active from 2013-04-30 to 2014-04-29
💬 Posted a total of 7 messages
📚 Participated in the following categories: Bitcoin-development, PATCH, try2
🔇 Please do not DM this user as it's used for archive purposes only.

Last Notes

2023-06-07 15:20:30

- reply

📅 Original date posted:2014-04-29
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We have BIP70 already in use (over a hundred paid requests).
Could you elaborate on why this needs changing?
On 28-04-14 14:39, Gavin Andresen wrote:
> There is a discussion about clarifying how BIP70 signs payment
> requests here: https://github.com/bitcoin/bips/pull/41
>
> The issue is what to do with the signature field before signing.
> The code Mike and I initially wrote does this:
>
> request.set_signature(string(""));
>
> (sets signature to the empty string)
>
> I think that is a mistake; it should be:
>
> request.clear_signature();
>
> (clears signature field, so it is not serialized at all).
>
> So: if you are implementing, or have implemented, the payment
> protocol, please chime in. I'd like to change the spec and the
> reference implementation NOW, while BIP70 is still a 'Draft'.
>
> Because this type of "hey, I'm implementing your standard and it
> doesn't work the way I think it should" mistake is exactly why BIPs
> take a while before being declared 'Final.'
>
>
>
>
> ------------------------------------------------------------------------------
>
>
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing
> platform available. Simple to use. Nothing to install. Get started
> now for free." http://p.sf.net/sfu/SauceLabs
>
>
>
> _______________________________________________ Bitcoin-development
> mailing list Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTX9bcAAoJELhWickZBkAlKqcH/RVFAr6vGgDjJvYah46StMHy
ZhKwpV1oqFCslOts6MyO+bZp9uDRlmYtnAy02CTPmlico3IyK85/+CGCGEdyiGo1
AEI2Ixr5FJs9t8uAVLyUKwOQddUFEJuZuiKXd1Wl9GqfG/z8gwdSxd08Wrq57lSH
JdwUnWOG1xBwyhgm7stqFoXgTrrnFNcE97vwsk6QMIzJG/v0suw7Lp42q7bKYaA/
J9xWSQ1cRKSPdsmu4K45oxXriqUmiqz3EouaTSQqC80OO7y8sfa96DqiHR83Vy3w
KUna5enjGqhhberWCokg3x5lCiH/IfLPrgK23iib4cg6Vm70jSQ2S2Xh/NuoDaM=
=JA5K
-----END PGP SIGNATURE-----

2023-06-07 15:12:15

- reply

📅 Original date posted:2014-01-18
📝 Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We rebroadcast incoming transactions without fees at several nodes,
including bc.info, to keep them in mempools.
On 01/17/2014 10:04 PM, Mark Friedenbach wrote:
> CPFP is *extremely* important. People have lost money because this
> feature is missing. I think it's critical that it makes it into
> 0.9
>
> If I get a low-priority donation from a blockchain.info wallet,
> that money can disappear if it doesn't make it into a block in 24
> hours - bc.i will forget the transaction and happily respend its
> inputs on the next transaction that user makes.
>
> I wouldn't mind paying $1 in fees to receive a $50 donation. But
> without CPFP there's no way to do that.
>
>
> On 01/17/2014 12:53 PM, Jeff Garzik wrote:
>> <vendor hat: on> BitPay sure would like to see CPFP in
>> upstream.
>
>> I think the main hurdle to merging was that various people
>> disagreed on various edge case handling and implementation
>> details, but no fundamental objections.
>
>
> ------------------------------------------------------------------------------
>
>
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In
> Between. Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
>
>
_______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQEcBAEBAgAGBQJS2mbQAAoJEIilnEpWGBYhH+8H/2nIZjrrZIPi/4ZeTi71cZOe
78oD4mzWM9zvRbjbGfIWrgTnkRQi4OQ/GorbRiyoAeKzAQ+SdeY8dkRsS14zpqpC
w4efoJOTxgi69giBWGPWlPvAtTwD65EcfJmUs5XeGi7J/3E0qTyry6sDu8t2ip84
hLUnqMOcNhc0J/k0KvBbEyl1YXcRWMjz5X2pMtY9yeMk+qFQPR1+RjZ+91OCRyui
Z47jhHlbhc5daXAWrq4fb54uNSJWUnYky7yN2pDTovAVq5PNNVNJTdxbjXSyYmcP
FwFNkARrgXRlSvf07FN991aa2u4CTkjRgA9uRrvcTtLXr8g2F0yymfPr0AQrgZg=
=J9Z4
-----END PGP SIGNATURE-----

2023-06-07 15:09:57

- reply

📅 Original date posted:2013-11-22
📝 Original message:Thanks a lot! I will run these patches on some nodes tomorrow to see if
it works.
On 22-11-13 21:49, Jeff Garzik wrote:
> Whitelist nodes against banning.
>
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing
> conversations that shape the rapidly evolving mobile landscape. Sign up now.
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

2023-06-07 15:09:09

- reply

📅 Original date posted:2013-11-06
📝 Original message:bounty++
On 06-11-13 06:33, kjj wrote:
> One of the things that really gets me going is when someone devises a
> model, tests it against itself, and then pretends that they've learned
> something about the real world.
>
> Naturally, the Selfish Mining paper is exactly this sort of nonsense.
> Their model is one with no latency, and one where the attacker has total
> visibility across the network. An iterated FSM is not a suitable
> simulation of the bitcoin system. The bitcoin network does not have
> states, and to the extent that you can pretend that we do, you can't
> simulate transitions between them with static probabilities.
>
> The authors understand this deep down inside, even though they didn't
> work out the implications. They handwave the issue by assuming a total
> sybil attack, and in true academic spirit, they don't realize that the
> condition necessary for the attack is far, far worse than the attack itself.
>
> Greg said he'd like to run some simulations, and I'm thinking about it
> too. Unfortunately, he is busy all week, and I'm lazy (and also busy
> for most of tomorrow).
>
> If neither of us get to it first, I'm willing to pitch in 1 BTC as a
> bounty for building a general bitcoin network simulator framework. The
> simulator should be able to account for latency between nodes, and
> ideally within a node. It needs to be able to simulate an attacker that
> owns varying fractions of the network, and make decisions based only on
> what the attacker actually knows. It needs to be able to simulate this
> "attack" and should be generic enough to be easily modified for other
> crazy schemes.
>
> (Bounty offer is serious, but expires in one year [based on the earliest
> timestamp that my mail server puts on this email], and /may/ be subject
> to change if the price on any reputable exchange breaks 1000 USD per BTC
> in that period.)
>
> Basically, the lack of a decent network simulator is what allowed this
> paper to get press. If the author had been able to see the importance
> of the stuff he was ignoring, we wouldn't be wasting so much time
> correcting him (and sadly the reporters that have no way to check his
> claims).
>
> https://bitcointalk.org/index.php?topic=324413.msg3495663#msg3495663
>
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models. Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

2023-06-07 15:05:38

- reply

📅 Original date posted:2013-08-14
📝 Original message:On 08/07/2013 11:10 PM, Gavin Andresen wrote:
> I'd also like to hear from merchants: any issue with your payment
> processing server having "broadcast transaction" functionality?
>
On the contrary, we would prefer to broadcast the transaction ourselves.

2023-06-07 15:02:56

- reply

📅 Original date posted:2013-06-06
📝 Original message:Abe is able to do what you want.
https://github.com/jtobey/bitcoin-abe
https://bitcointalk.org/index.php?topic=22785.0
With kind regards,
Jouke Hofman
Bitonic.nl
On 06/06/2013 02:53 AM, Marko Otbalkana wrote:
> Could anyone point me to work/project(s) related to storing the block
> chain in a database, like PostgreSQL, MySQL? How about any tools that
> can read the block chain from the Satoshi client and convert it into
> different formats?
>
> Thanks,
> -Marko
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
>
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>