Other·Unmonitored61d agoYUNA-CLAIM:465c6b3232757dd509c8c9629a5cf03e32345a0d2fe884e1a082ee947f65de0b▲0▼#965,566 · bc1pdlh8c0…kzm8 · 0.7 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:43c946f835aaade4fbf1f1b9399bbd89c4e03776f4fbd671ccd6678d94e53b63▲0▼#965,566 · bc1pf4hll4…yfpr · 0.7 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:b99be58b441eee2d4e9a26607cf1e0fb557dcfb646318fe8eb749550e9c2e33c▲0▼#965,559 · bc1pw4alua…yx7u · 0.7 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:88e481ca38a7c2f96a585924ea54045d0f49b57ccef1a2e1206394823d8aa558▲0▼#965,543 · bc1pr005de…ccw7 · 2 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:eb86d7fbf9dfa67668c082fcc6f7f183e4f0a7a695aecd3f06d39aaa4534c3b4▲0▼#965,543 · bc1q99e6c9…fjtv · 2 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:b8638dcfc93381999da4e3305c8e72ec2785a90c022cfd0b93302f95b834416f▲0▼#965,543 · bc1pmk3w90…xuz9 · 2.2 sat/vBOpen →
Other·Unmonitored61d agoFrom:satoshiSubject:Re: Dealing with SHA-256 CollisionsDate:June 14, 2010 at 20:39:50 UTCSHA-256 is very strong. It's not like the incremental step from MD5 to SHA1. It can last several decades unless there's some massive breakthrough attack.If SHA-256 became completely broken, I think we could come to some agreement about what the honest block chain was before the trouble started, lock that in and continue from there with a new hash function.If the hash breakdown came gradually, we could transition to a new hash in an orderly way. The software would be programmed to start using a new hash after a certain block number. Everyone would have to upgrade by that time. The software could save the new hash of all the old blocks to make sure a different block with the same old hash can't be used.… read full message →▲0▼#965,529 · bc1qkhqlk3…2t8f · 1 sat/vBOpen →
Other·Unmonitored×261d agot 0 1 a400abafc962dc8cc95aa047a8cd000bd03cbc82b38f2415ee4a48c32119b1b4 0▲0▼#965,529 · 1PKcYrUHZo…tykR · 1.6 sat/vBOpen →
Other·Unmonitored61d agot 0 1 a400abafc962dc8cc95aa047a8cd000bd03cbc82b38f2415ee4a48c32119b1b4 0▲0▼#965,529 · 19y6Sr1Fkb…VeG6 · 1.6 sat/vBOpen →
Other·Unmonitored61d agot 0 1 fbc43253c19da784255dcee5109b02b66df78e226eba14d9d98d06968eb46352 0▲0▼#965,529 · 1ERkPtnuc6…gkrP · 1.6 sat/vBOpen →
Other·Unmonitored61d agoMaking the OP_RETURN exceed 83 bytes so the transaction won't be replayed in the Blake hard fork. Making the OP_RETURN exceed 83 bytes so the transaction won't be replayed in the Blake hard fork.▲0▼#965,521 · bc1qy2k4kr…pp3q · 0.4 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:18374af3aeccdf08d4e555f59ec6b882eb2ce5e74708ecb93427742d616e2347▲0▼#965,511 · bc1qhnc05n…609m · 2.7 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:8f1e167637dd5c36dbc332b99cca0d3256cd2df016631119f495c82ff16d28f2▲0▼#965,511 · bc1q0dngwp…p8lz · 2.7 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:ffadd3430c1d19e6d800c267b1aa5ec5269655a6c62c1ad245fa50e67debee0c▲0▼#965,511 · bc1pt0hmre…ex0u · 2 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:284e5c0e79f30e4d35dabceacd1464dbb4294c020506be143616eef7217e0478▲0▼#965,510 · bc1pn8579k…407e · 3.2 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:24a47e0517bd64447531f0320694de4fcd835e0e134d52194e5754d91160971c▲0▼#965,508 · 3GEqeyCs14…4cqW · 3.5 sat/vBOpen →
Other·Unmonitored61d agoYUNA-CLAIM:7f2ff09e3a0e4a50e0c99994488ce231f66508e31c6d8bef2fb381ff07fd9791▲0▼#965,506 · 3GQGoKMs2F…DVoZ · 4.5 sat/vBOpen →