2,059 karma · joined July 22, 2010
jon@jonb.org
meet.hn/city/kr-Seoul
Socials:
- x.com/jbaudanza - github.com/jbaudanza
Interests:
AI/ML, Mobile Development, Open Source, Programming, Startups
---
I'm not sure what specific meaning you've assigned to the word hate. In my mind, hating an idea is not a fatal personality flaw.
This transaction is embedding a message inside of a non-standard output script, which shouldn't be possible.
Hope this helps.
1) Whoever did this has access to enough hashing power to mine their own non-standard transactions into blocks.
2) $0.43 is unusually high for a transaction fee. Perhaps this is high enough to incentivize miners to include the tx in a block.
From a3a61fef43309b9fb23225df7910b03afc5465b9 Mon Sep 17 00:00:00 2001
From: Satoshi Nakamoto <satoshin@gmx.com>
Date: Mon, 12 Aug 2013 02:28:02 -0200
Subject: [PATCH] Remove (SINGLE|DOUBLE)BYTE
I removed this from Bitcoin in f1e1fb4bdef878c8fc1564fa418d44e7541a7e83
in Sept 7 2010, almost three years ago. Be warned that I have not
actually tested this patch.
---
backends/bitcoind/deserialize.py | 8 +-------
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/backends/bitcoind/deserialize.py b/backends/bitcoind/deserialize.py
index 6620583..89b9b1b 100644
--- a/backends/bitcoind/deserialize.py
+++ b/backends/bitcoind/deserialize.py
@@ -280,10 +280,8 @@ opcodes = Enumeration("Opcodes", [
"OP_WITHIN", "OP_RIPEMD160", "OP_SHA1", "OP_SHA256", "OP_HASH160",
"OP_HASH256", "OP_CODESEPARATOR", "OP_CHECKSIG", "OP_CHECKSIGVERIFY", "OP_CHECKMULTISIG",
"OP_CHECKMULTISIGVERIFY",
- ("OP_SINGLEBYTE_END", 0xF0),
- ("OP_DOUBLEBYTE_BEGIN", 0xF000),
"OP_PUBKEY", "OP_PUBKEYHASH",
- ("OP_INVALIDOPCODE", 0xFFFF),
+ ("OP_INVALIDOPCODE", 0xFF),
])
@@ -293,10 +291,6 @@ def script_GetOp(bytes):
vch = None
opcode = ord(bytes[i])
i += 1
- if opcode >= opcodes.OP_SINGLEBYTE_END and i < len(bytes):
- opcode <<= 8
- opcode |= ord(bytes[i])
- i += 1
if opcode <= opcodes.OP_PUSHDATA4:
nSize = opcode
--
1.7.9.4http://putyourbeardinmymouth.tumblr.com/post/14184840145/uhh...
https://github.com/igrigorik/hackernews-button
This new one seems more extensible though. I may give it a try next time I update my blog.
How can we prevent this? Some ideas so far:
- Moderation
- Give people specific tasks: "Find this duffle bag" (thanks shocks)
What else?
The advantage of evented I/O is that you don't have to do either of these things.
If your app takes up 256MB, does that mean you can only fit 2 workers? Shouldn't there be some savings due to copy-on-write?
But in this case, as long as you expect your database requests to be fast and reliable, it's fine to mix in the standard blocking pg driver.
To account for this, I created a controller mixin to recreate the middleware stack for responses:
The danger is that there are far more essential nutrients that we don't know about, than nutrients that we do. And the only way to get these nutrients is to eat a well balanced diet.
That being said, this would be amazing if it works and I applaud him for trying.