I hereby claim:
- I am petertodd on github.
- I am petertodd (https://keybase.io/petertodd) on keybase.
- I have a public key whose fingerprint is 37EC 7D7B 0A21 7CDB 4B4E 007E 7FAB 1142 67E4 FA04
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
> - floating ADC inputs, as Peter suggested; | |
> - five independent RC oscillators. | |
I've got another idea that requires no extra hardware. I think has a | |
solid theoretical basis which I've explored below in sufficient detail | |
to raise suspicions that I miss my old line of work: | |
tl;dr: Record the dt time between button clicks, adding dt to the | |
accumulator each time by hashing it into the persistent state. |
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and bug fixes.
Please report bugs using the issue tracker at github:
#!/usr/bin/python3 | |
class CMemPoolTx: | |
@property | |
def feerate(self): | |
return self.nFee / self.nSize | |
@property | |
def sum_feerate(self): | |
return self.nSumFees / self.nSumSize |
#!/usr/bin/python3 | |
import os | |
import sys | |
import struct | |
from opentimestamps._internal import hexlify,unhexlify | |
import opentimestamps._bitcoinrpc as btcrpc |
bar |
The following is licensed as CC0. Feel free to copy it for your own purposes, with or without acknowleding my authorship. | |
--- | |
layout: post | |
title: "The Misleading and Inaccurate Claims Made to Tierion ICO Investors" | |
tags: | |
- tierion | |
- ico | |
- timestamping | |
--- |
Anonymous identities are cheap. Suppose you are running a wiki, and are having a problem with spammers, trolls, and other abusive people. Now you can of course ban accounts for abuse, but this is the internet, creating a new account is trivial. This is especially true when you want to allow anonymous use of your wiki. (or for that matter, any service) Of course you can try to make it harder to make a replacement account with efforts like captchas and requiring email addresses from well-known domains, but these solutions all have drawbacks, and are often surprisingly easy for spammers and trolls to defeat. (you can hire humans to solve captchas for you at remarkably low rates)
Fundementally all those solutions are making an identity more expensive to get. Of course, you could just charge membership fees - Something Awful, 4chan and the Bitcoin Wiki all do this - but now you're running a business and users have to pay fees for every wiki they join. What you really want is some sort of
Return-Path: <calidadlsp@casanare.gov.co> | |
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on | |
ip-172-30-0-206.ec2.internal | |
X-Spam-Level: | |
X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,DKIM_SIGNED, | |
DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FORGED_REPLYTO, | |
FREEMAIL_REPLYTO_END_DIGIT,HTML_MESSAGE,SPF_PASS autolearn=no | |
autolearn_force=no version=3.4.2 | |
X-Original-To: pete@petertodd.org | |
Delivered-To: pete@petertodd.org |