OP_DATA_32(32) 42c3ddd0c90a5644013b524e1fd139b3ee9a3adef356e85c5a03746cfa7a61df

OP_CHECKSIG(172)

OP_0(0)

OP_IF(99)

OP_DATA_3(3) ord

OP_DATA_1(1)

OP_DATA_16(16) application/json

OP_0(0)

OP_PUSHDATA2(77) {"subject":"Development of alert system","content":{"format":"html","body":"\u003cdiv class=\"post\"\u003eI've been working on writing the alert system. \u0026nbsp;Alerts are broadcast through the network and apply to a range of version numbers. \u0026nbsp;Alert messages are signed with a private key that only I have.\u003cbr/\u003e\u003cbr/\u003eNodes can do two things in response to an alert:\u003cbr/\u003e- Put a warning message on the status bar.\u003cbr/\u003e- Make the money handling methods of the json-rpc i

OP_PUSHDATA2(77) nterface return an error.\u003cbr/\u003e\u003cbr/\u003eIn cases like the overflow bug or a fork where users may not be able to trust received payments, the alert should keep old versions mostly safe until they upgrade. \u0026nbsp;Manual users should notice the status bar warning when looking for received payments, and the json-rpc safe mode stops automated websites from making any more trades until they're upgraded.\u003cbr/\u003e\u003cbr/\u003eThe json-rpc methods that return errors during an alert are:\u003cbr/\u

OP_PUSHDATA2(77) 003esendtoaddress\u003cbr/\u003egetbalance\u003cbr/\u003egetreceivedbyaddress\u003cbr/\u003egetreceivedbylabel\u003cbr/\u003elistreceivedbyaddress\u003cbr/\u003elistreceivedbylabel\u003cbr/\u003e\u003cbr/\u003e\u003c/div\u003e"},"source":{"name":"Bitcoin Forum","url":"https://bitcointalk.org/index.php?topic=898.msg10722#msg10722"},"date":"2010-08-22T23:55:06Z"}

OP_ENDIF(104)