Print Page - Nullian Verification: Post your PGP keys and timestamped statements here!

Title: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on March 15, 2020, 10:04:06 PM

Be élite! Use crypto!

See also relevant technical discussion (https://bitcointalk.org/index.php?topic=5244365.0) of the future of Nullian Verification.

I now invite others to post their own verification statements on this thread. If I can get at least a few others doing this regularly, then I will start a git repository with timestamped signed attestations of my own observations of what was posted by what account, and push it to Github. That way, everybody will be able to pull all of the substantive data from this thread (including a collection of PGP keys) conveniently, without tedious and error-prone copying and pasting from a forum thread.

Please refer to my 2020-04-28 statement (https://bitcointalk.org/index.php?topic=5233083.msg54320576#msg54320576) for a reference on how this should be done. Expressed in pseudocode, v0.0.1-alpha of the required format is:

Code:

"Bitcoin Forum name:\t[your name]\n"
"Bitcoin Forum userid:\t[your userid]\n"
"PGP primary key:\t[your PGP fingerprint]\n"
"\n"
"# Ten most-recent Bitcoin block hashes:\n"
"\n"
"[height]\t[ISO date]\t[hex hash]\n"
[...]

That is human-readable; and I think that it should be not too horrible to wrangle with /bin/sh and standard shell tools.

DO NOT include the date, which is contained in the Signature Creation Time (https://tools.ietf.org/html/rfc4880#section-5.2.3.4) subpacket of your PGP signature. DO NOT include any other extraneous data that may confuse scripts.

Include a complete OTS file, base64ed in a separate <code> block. Posts without a timestamp file will be deleted.

For your first post on this thread, and any time that your PGP is updated, please include your PGP key in a separate <code> block. If desired, you may also include links to archival evidence that you have previously claimed the same PGP primary key with the same forum account; if you do, keep any descriptions concise and factual.

I plan to invite third parties to attest which accounts they see posting what; however, that will need to wait for me to develop a reasonable format for it. DO NOT quote other people’s posts here; quote-posts will be silently deleted.

DO NOT post claims to have verified others’ signatures and timestamps! Such claims encourage newbies to believe Gavin-style fake “verifiations”. I will delete all such claims from this thread.

Anybody may post properly formatted verification statements, timestamps, and PGP keys on this thread. However, all discussion is off-topic; posts containing any kind of chit-chat will be deleted without comment. If you wish to engage in expert-level technical discussion of a better way to do this, please take it up on my relevant thread in Development & Technical Discussion (http://). Otherwise, please wait for that better way to be developed.

Original post text, with updated list of links to statements:

Much have I complained about the ad hoc security measures in the various “stake” threads. Well, I should offer a better solution. Here it is—at least, the start of something better. I intend to do this semi-regularly—at least once per month, unless I am “sleeping”.

If my forum account has posted recently, and significantly more than a month has passed since this thread was refreshed with a new PGP-signed, OTS-timestamped message containing verifiably recent information, then you should demand a fresh statement consistent in its evidentiary strength with the statements that I have previously provided. Be very suspicious if the demand is refused or ignored.

I intend to refine my way of doing this, based on future experience. If or when I work out a standard format that is relatively easy for others to fully verify, then I may open a new “stake” thread where quoting is prohibited as spam, and trustless, cryptographically verifiable evidence is required in a standardized, easy-to-verify format.

Verification statements (listed in reverse chronological order):

Signing time: 2020-11-25 18:49:42 (#post_november)
Signing time: 2020-10-24 22:51:37 (#post_october)
Signing time: 2020-09-25 12:43:57 (#post_september)
Signing time: 2020-08-26 00:16:32 (https://bitcointalk.org/index.php?topic=5233083.msg55067299#msg55067299)
Signing time: 2020-04-28 22:49:29; timestamp block height: 628068 (https://bitcointalk.org/index.php?topic=5233083.msg54320576#msg54320576)
Signing time: 2020-04-16 22:58:41; timestamp block height: 626332 (https://bitcointalk.org/index.php?topic=5233083.msg54237753#msg54237753)
Signing time: 2020-03-15 20:22:35; timestamp block height: 621774 (https://bitcointalk.org/index.php?topic=5233083.msg54036153#msg54036153)

Local rules: Only the following are on-topic in this thread. Anything else will be silently deleted as off-topic.

~~New signed and timestamped statements from me.~~
~~Smart questions (http://www.catb.org/~esr/faqs/smart-questions.html) stated with at least ordinary social courtesy.~~
Competent technical questions, comments, suggestions, or critiques. I welcome competent technical discussion! However, I am currently out of patience with people who make repeated incorrect assertions out of ignorance, even when I provide something tantamount to a free tutorial.

Do not publicly say that you have verified a statement. This gives a false sense of security, and tends to inculcate in the public a habit of relying others to “verify” (https://bitcointalk.org/index.php?topic=5215128.msg53826983#msg53826983), instead of verifying for themselves. This is crypto! It is supposed to be trustless. Discussion of how to verify these things is welcome—claims that you have verified something are not.

If you want to post a similar statement yourself, please e-mail or PM me first to discuss it. The way that I am doing this is admittedly a bit rough; and I don’t want to start a trend before improving that, perhaps with your suggestions. Thanks.

Title: Re: Nullian Verification
Post by: nullius on March 15, 2020, 10:04:24 PM

reserved

Title: Re: Nullian Verification
Post by: nullius on March 15, 2020, 10:45:48 PM

For the purpose of proving that a digitally signed statement has not been backdated, I hereby present a tool far superior to quoting and archiving: Secure, trustless timestamps using the Bitcoin blockchain!

Understand what OpenTimestamps does and does not prove. Peter Todd’s announcement blog post (https://petertodd.org/2016/opentimestamps-announcement) provides an excellent introduction.

In the digitally signed message presented below, I include recent information that would be infeasible to predict. This prevents forward-dating, which OpenTimestamps itself does not prevent. The information within the message is strong evidence that the message was created and signed not significantly before its alleged creation time; the timestamp trustlessly, verifiably proves that the message was created and signed not significantly after its alleged creation time.

The magic bits are contained in an OP_RETURN in txid:
134da08e1590e709f3904e91e05de0e839bab18c5ad456471d0f3c84f374ae20
Need a handy explorer link? See Blockstream.info (https://blockstream.info/tx/134da08e1590e709f3904e91e05de0e839bab18c5ad456471d0f3c84f374ae20) (Javascript required; onion (http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/tx/134da08e1590e709f3904e91e05de0e839bab18c5ad456471d0f3c84f374ae20)).

As a practical matter, the only thing that you that need to verify the timestamp is the timestamp file that I have base64ed below (plus of course, the timestamped file). You can verify this locally, using the OpenTimestamps client (https://github.com/opentimestamps/opentimestamps-client) plus your own Bitcoin node, or verify it on the OpenTimestamps website (https://opentimestamps.org/) if you trust it to tell you the truth. :-)

The timestamped file:

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I am Bitcoin Forum user 976210.

To provide evidence that this is not an old message previously signed
and forward-dated, I will hereby cite the three most recent posts by
theymos (weaker evidence, especially since he hasn’t posted in a few
days), and the ten most recent Bitcoin block hashes (stronger evidence!).

To prevent this message from being altered and backdated in the future,
I will timestamp it with Peter Todd’s OpenTimestamps service.  This in
itself will provide security incomparably superior to the forum tradition
of “quote and archive”.

I will NOT hereby state the signing time, or the identity of the signer.
You should obtain this information from the PGP signature on this message.

- ----

# Three most recent posts by theymos

https://bitcointalk.org/index.php?action=profile;u=35;sa=showPosts

Other / Politics & Society / Re: Coronavirus Outbreak
on: March 12, 2020, 10:01:13 PM
https://bitcointalk.org/index.php?topic=5220206.msg54017323#msg54017323

Other / Politics & Society / Re: 2020 Democrats
on: March 11, 2020, 12:53:05 AM
https://bitcointalk.org/index.php?topic=5112320.msg54004736#msg54004736

Other / Politics & Society / Re: Tax rebates to reflate the economy.
on: March 11, 2020, 12:45:13 AM
https://bitcointalk.org/index.php?topic=5231748.msg54004716#msg54004716

- ----

# Ten most recent Bitcoin block hashes:

000000000000000000003e0f3a098ea6e92fe2c474538d58afe38c8b24956eb4
Block Height:	621772
Timestamp:	2020-03-15 20:18:19

0000000000000000000f8444e1ac4fea06b9b75be7b045f3d2fecacdcb5c4b79
Block Height:	621771
Timestamp:	2020-03-15 20:09:48

00000000000000000004045d8d72ba911e03d9ed55be24344b6599d705169061
Block Height:	621770
Timestamp:	2020-03-15 20:07:02

0000000000000000000398f192ab9d1c8056f16000a669d7475e4c29c0571b09
Block Height:	621769
Timestamp:	2020-03-15 19:45:38

0000000000000000000992b96449d86cce2358cfd3db015fe211475be63ceaa5
Block Height:	621768
Timestamp:	2020-03-15 19:20:55

00000000000000000000ba33260d466b09fcc69fac83869c4e3c355f788eb8a9
Block Height:	621767
Timestamp:	2020-03-15 19:15:28

0000000000000000000d12afb75eb77f4705ca95ebbaaf8b3add45209965d525
Block Height:	621766
Timestamp:	2020-03-15 19:05:51

0000000000000000000ad77af87316d3e95c988e7c6ae99b93af4e0eb68b6538
Block Height:	621765
Timestamp:	2020-03-15 18:56:13

0000000000000000000650e6d97be40d26ff0bf4f61ad27e28cb541fdda37302
Block Height:	621764
Timestamp:	2020-03-15 18:54:47

00000000000000000009fc68e0faee77640280270f79b61fed0fc4a0af85f479
Block Height:	621763
Timestamp:	2020-03-15 18:53:22

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSNOMR84IlYpr/EF5vEJ5MVn575SQUCXm6OiwAKCRDEJ5MVn575
SRCeAPwMr7wHtRwREzQLf0tznVQXVjJSPZD4IcRyDMPFB9HyPQD7BMZfzJ+Ize5q
2XQFV9sZOYpZ5keSss3Q5RLnyhJO8gc=
=gsBL
-----END PGP SIGNATURE-----

To verify the timestamp, you must save the signed statement with Unix line endings ('\n') and a single final line-terminator on the last line. (No blank line at the end.)

The OTS file (base64ed):

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEI9sq0yyHNA7Oc7SjJ7gQx
qRm2dNn7S/MHAWTW00a20jvwEFhohSNdXDR856fKQXHO5KoI//AQO52Bcij3aHIZ
WOfJVznYTAjxBF5uj2nwCAw5p+1O4DH7AIPf4w0u+QyOLi1odHRwczovL2FsaWNl
LmJ0Yy5jYWxlbmRhci5vcGVudGltZXN0YW1wcy5vcmf/8BBbfhwjdFJu0V6bF3yG
3gBhCPEEXm6PafAIoXUfhzN6AogAg9/jDS75DI4sK2h0dHBzOi8vYm9iLmJ0Yy5j
YWxlbmRhci5vcGVudGltZXN0YW1wcy5vcmf/8BDGkXigQDsv44GSxwVKQtQzCPEE
Xm6PafAIoLPTIM9Qomz/AIPf4w0u+QyOIyJodHRwczovL2J0Yy5jYWxlbmRhci5j
YXRhbGxheHkuY29tCPEgGVR3dUW3/QtHqmx9l4EwFriGWIh7WFUAmRgEG8WB740I
8SB3yInee0NLimTtDyD4sosIV3Q3fhtUT8IePlFpBFMpgwjxIIXhLAjZka3qEqVT
RTVF/o3KaLOnC2sh01mRSukyIxg+CPAgxPMFC51GEMTwsNfcDqzstCuBia3awh/a
XWDSeANQGCMI8SCH0Ml/xktDPgkvTJeQg2u5T0HL2xN54pr6XzbjovKFBQjxIDog
f16bcybb8BeQT2Qx1L3jPuKtMDYiRBTWUf6HpdNNCPFxAQAAAAFV2vsDrtn4wNHz
7BJL5LpuviA07ClHKku118Yl22QvEQAAAAAXFgAUxZeyBglbKHzv67mWu0GJUSd1
uvz9////AqlEHwAAAAAAF6kUUX9272bseU9ljqWMSKagCJpBLbWHAAAAAAAAAAAi
aiDwBM18CQAICPAgeEGiiWkoSIF79wnRyWhfse4A5L4kxIKUigLbYqdqhfEICPAg
bRcFRYD1rRBlh9LOgAFLtHydT+WUznsq1892G4mJ1NcICPAg3YziPI7XC0vRMn3Z
GTjXWWoXIutqKJx4lOIhzPZvM7kICPEg8fknVqeXAlNrqBJaursNd3iSoDerQ57J
SBN2LhuQ31EICPEgGMBRXtEFVxx6o2Vrf+le4pDbp6bX0LtWOYxlqb6Cc7gICPEg
jXEJpwsBiK8UboiPY6PAZAX6rt+dTsPV6ISIO2g0R9oICPAgSZJPUTiX0gA/BepF
awrAp3sPYJiXeBG57s3eNmyT9koICPAg7gUR/MFM4nHe/L/hf78xWZdDX10gfwnL
PrDOjt9XDAQICPAgOHx7lGj9IeIvVt7u+2pGzJKHY/VBbb7vDuJOhRyiWq0ICPEg
wdAFI+AlMByatqv31tAkXapwLYAt2LbKeimJty5HOeQICPEgp+KcJTFiVMpCVCAB
6wpe8T1GuOlX5VXoSD6R/aISI1IICAAFiJYNc9cZAQPO+SXwENTi/oDG+bCDAnFO
AlKGBUQI8QRebo9p8AhzsdE8fRHnsgCD3+MNLvkMjikoaHR0cHM6Ly9maW5uZXku
Y2FsZW5kYXIuZXRlcm5pdHl3YWxsLmNvbQ==

I waited for this to get sufficient Bitcoin confirmations that it may be considered to be reliably buried. I also “upgraded” the file, so that it contains all the information that you need to verify it with reference to the blockchain. You will be able to verify this timestamp even if the OpenTimestamps website and the calendar servers all disappear. As long as Bitcoin exists, this timestamp will remain secure and trustlessly verifiable.

Title: Re: Nullian Verification
Post by: nullius on April 17, 2020, 12:22:12 AM

Signing time: 2020-04-16 22:58:41; timestamp block height: 626332

The timestamped file:

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I am Bitcoin Forum user 976210.

To provide evidence that this is not an old message previously signed
and forward-dated, I will hereby cite a few of the most recent posts by
theymos (weaker evidence, especially since he hasn’t posted in a few
days), and the ten most recent Bitcoin block hashes (stronger evidence!).

To prevent this message from being altered and backdated in the future,
I will timestamp it with Peter Todd’s OpenTimestamps service.  This in
itself will provide security incomparably superior to the forum tradition
of “quote and archive”.

I will NOT hereby state the signing time, or the identity of the signer.
You should obtain this information from the PGP signature on this message.

- ----

# Most recent posts by theymos

https://bitcointalk.org/index.php?action=profile;u=35;sa=showPosts

Other / Meta / Re: delevic was banned by mistake
on: April 14, 2020, 09:49:55 PM
https://bitcointalk.org/index.php?topic=5239709.msg54222870#msg54222870

Other / Meta / Re: Theymos, may be a custom title please.
on: April 13, 2020, 08:04:20 PM
https://bitcointalk.org/index.php?topic=5239632.msg54215408#msg54215408

Other / Meta / Re: delevic was banned by mistake
on: April 13, 2020, 06:56:20 PM
https://bitcointalk.org/index.php?topic=5239709.msg54215057#msg54215057

Other / Meta / Re: [table] limits on Bitcointalk (?)
on: April 10, 2020, 08:34:50 PM
https://bitcointalk.org/index.php?topic=1782341.msg54196225#msg54196225

- ----

# Ten most recent Bitcoin block hashes:

0000000000000000000eb9f27a36e02843d2689982534049f76b3983ed85b1bf
Block Height:	626329
Timestamp:	2020-04-16 22:56:31

00000000000000000007fc5d607402a0c94209654343f3b811988c50e7f9f00b
Block Height:	626328
Timestamp:	2020-04-16 22:47:43

00000000000000000001df6cfcd7438741da5ba537e49012fee1f0d657203c27
Block Height:	626327
Timestamp:	2020-04-16 21:37:24

00000000000000000010189e996a082c2b14b9153a48fcdfe2d52941b4d8e4ab
Block Height:	626326
Timestamp:	2020-04-16 21:30:09

00000000000000000006a6f44f8fd73b795566419e4f53a86898b15970068fdf
Block Height:	626325
Timestamp:	2020-04-16 21:25:43

00000000000000000002ec00babeff6e29c34bc9dfaac9c5ab3d4adc4c5b4f7c
Block Height:	626324
Timestamp:	2020-04-16 21:25:05

00000000000000000007656fb4e3e2793d338ec69a38a3dba3f440dd376b5145
Block Height:	626323
Timestamp:	2020-04-16 21:03:54

000000000000000000022df72f795f4a931eaf95d8a585a2666bd2608f753d7e
Block Height:	626322
Timestamp:	2020-04-16 20:55:55

0000000000000000000b076ad877866dd3c58b79d3f4a6d7b9bdd2a24b74c7cb
Block Height:	626321
Timestamp:	2020-04-16 20:54:02

0000000000000000000584d979e0b41ce2cce0d598ff7535a5ae079978ab0435
Block Height:	626320
Timestamp:	2020-04-16 20:52:34

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSNOMR84IlYpr/EF5vEJ5MVn575SQUCXpjjIQAKCRDEJ5MVn575
SRAYAQDoE7P4NcORiTsgwQvFBjUTQ2KhISGYPZ60K7xvRm3QgwD/VUDdpyca+xO6
PKkKUJx5kvNaBhPZTWVou0dSIXu0rwY=
=BjCn
-----END PGP SIGNATURE-----

To verify the timestamp, you must save the signed statement with Unix line endings ('\n') and a single final line-terminator on the last line. (No blank line at the end.) Exclusively for ease of checking that the file is saved correctly, here is its SHA256 hash:

Code:

c17a2370bafe895eaec2df0e055c019066cb7527e085679c3baeb893fd6329ca

The OTS file (base64ed):

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIwXojcLr+iV6uwt8OBVwB
kGbLdSfghWecO664k/1jKcrwEE0vzW/mutk3xmN7cw6VHI4I//AQAPXU9S/KZDPO
gnERigYgFwjxBF6Y40XwCKVT1ByUxA+N/wCD3+MNLvkMji4taHR0cHM6Ly9hbGlj
ZS5idGMuY2FsZW5kYXIub3BlbnRpbWVzdGFtcHMub3JnCPAgFts13B6xukJiXkuK
pZL8P5VAkpB8/xBQuam9p1LHjjUI8SA2qZ/zheDKJmxPUpzpJBGfP2oqHi68Euwl
bwTfsM13EgjwIHMXStJ8YIcsk+8TTuKvqewMjUD4MYvuYja4wR2SpfUICPEgXEZ3
iu2L8gZ37d6w0BnVfXLUApUUNWZPb1uosebH9HII8CBogT60GA2l4MkGcPWBGDKL
67itrgz18a09MnjjgSEPTQjxIH2yTE4yXF/dsX7IDb5I53mfJXZKWIiaEiPlunKu
iR/tCPEglZfRlWb388ZEfKKxWKdiN1xvPt+B6oWyIOx0B/k6V+EI8SDP0Hh7QAvj
gdeGpQGTRM3RZ6E4iz6lSKgzVjNlOViIIAjxIJYLeVAdJft00AibeV45mIoNdf/Z
PlAO9xjBfOU265LFCPEgA1SrCI4mGTYsqKQiGXs0qM2i4QzKZ+HbZhb5c9DqMSgI
8VkBAAAAAdGEYJ5JJI1ScXbgdDLMpDVXyCqq0S5cjRGUDMZosr69AAAAAAD9////
AlyqBAAAAAAAFgAUDnlCPFktyjzJPwV34Stxo0CxM+AAAAAAAAAAACJqIPAEm44J
AAgI8SAziAtbMLV/HKlld1RgAQMGNhyJcA3j0OM5Uow9cbekHQgI8SDO9nkafUtX
RGBQvRenz+9bKyMhZEx2EymwFduv5Ag7AQgI8SB066Gd5yt1ygx4JYU+YNIGlSeZ
El46cV+x2bGcGtcfgQgI8CAlfEVHM5+RXAjwWMZwdPjmMUk4ILS1mG3lUY21RA+P
rwgI8CADYMXfynmvONvvGbnMXhXx5RKM7Lj8z2Dbh+p/Jl999wgI8CA41PDtIPSb
mupbslE24kwqLd34BcseY6gD/Kv25Z3ULQgI8SDak6h+zi4m/H53lP7s70nQ6oZq
6GG/1SqOFctD4CuzmQgI8CBhr7mzxS6Ea/yEtyNnUozck9lhzxplTxqLnZP5Y/Vz
+wgI8CCB/MYBSOMXMz1h2qnJYuGJcLkXIPrdSau5n1k4jei68wgI8CCF9kwTV5NO
0VaIkiAyKvKFDrGTahwPndUKDEQDz3PXMQgI8CA8Gx9iPhoMxtIxb2b8A6w8og4W
TNZylESh760e4u9RvQgI8SC25IUfNnRHvJrdCEH+VEviDR8KmOnbQDx9EW+HJPQj
jggIAAWIlg1z1xkBA5ydJv/wEPHZ8iPgoVRoUmB+SPJC9TcI8QRemONE8AhBmDFb
od1CtgCD3+MNLvkMjiwraHR0cHM6Ly9ib2IuYnRjLmNhbGVuZGFyLm9wZW50aW1l
c3RhbXBzLm9yZ/AQ80e0DIYC/fVeUU96j2v1SgjxBF6Y40TwCK19EO5rg84UAIPf
4w0u+QyOIyJodHRwczovL2J0Yy5jYWxlbmRhci5jYXRhbGxheHkuY29t

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on April 28, 2020, 11:58:03 PM

Signing time: 2020-04-28 22:49:29; timestamp block height: 628068

The timestamped file:

Code:

Code:

b2d6ad0b970b66615a25dae0d44a810bb0b086fd767f0fd6ad6193a2fbf46e5a

The OTS file (base64ed):

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIstatC5cLZmFaJdrg1EqB
C7Cwhv12fw/WrWGTovv0blrwEBKBtnlXcnw/qEHSvyw0gEYI//AQeyeW7n2t0TRA
f0V35pO39AjxBF6osynwCCwbUci07rgiAIPf4w0u+QyOLCtodHRwczovL2JvYi5i
dGMuY2FsZW5kYXIub3BlbnRpbWVzdGFtcHMub3Jn//AQ03QRDCYHp0nDn6BCDM50
GAjxBF6osynwCJY7OZqNprHNAIPf4w0u+QyOIyJodHRwczovL2J0Yy5jYWxlbmRh
ci5jYXRhbGxheHkuY29t//AQ2icZUHPKkdkP0tomJtFV8gjxBF6osyjwCHfcTQQG
OhBF/wCD3+MNLvkMji4taHR0cHM6Ly9hbGljZS5idGMuY2FsZW5kYXIub3BlbnRp
bWVzdGFtcHMub3JnCPAg3ftGLa7q47J614rUQPcb783mMXh9sfJaLbcQSI+lYlgI
8SCjXhpgPj9EE+Wa/R8QAgn2LeUQiwoVVEAvUVlLbi+tDgjwIKaSav9c2Anii0dp
bu3/uxA1Z8VGNgdyutEmQN8OIkIaCPAgy7/BzPwG/o3ScAkhcjW7Of8NpeENsg0L
2sUL4eJhJa0I8CDwuOE8tfBsUs0sQapJloZnBxWtvixABU3ogp6ns5TLmwjwIJ6T
D7iWN6piqDAnLCFzNnjCpDyiAK+LVzeyPTsaTdi+CPAgEOfq8ak6uXRMs6yJCj6s
K0N24qgH89F2uTz6acEHFX0I8SAhRm4nsOmcLI2ogr0+yRXOxvwDLyDAXOd3VUZR
UmkahwjxINR9Y7Ns1fKta2XkxzL347LtWfrAgkR9kViYJXe8rkfTCPEgaWu+BIST
aaXRNdsKA6wwGj4UQE01kso4fmG+K1/lvgoI8SAhsnOfOX3aOGKHEKooQMESNLlv
tg2lrTajvaL8AhhlLAjwIKqrGrBoqJXUl7VcSz3hUMi2QSRiUz1UFQv/1/Utc4Un
CPFZAQAAAAHQ48ukdhcyOFrVnzdtKAA/Cm76sl5wx1O/dNmSE0DuVAAAAAAA/f//
/wKobgQAAAAAABYAFNHURSEdT72kunGgMl/srlf8SED2AAAAAAAAAAAiaiDwBGOV
CQAICPAg6mBwL9fMtCAuOZN41MH5QhaIhK+LzgbOyMzy20Su7FwICPEgPX3e/NsO
SWPmlZuDbbezFiQaiAQjL0Zlrna7qTzk9YYICPAgvfP+jJ9N6+EXNSezLT7WhqEc
Vzsf+yohRf257RaVNnIICPEg7bXZRRN41yR5rIoBPltimlgAtnuBUYa10fyzU+vP
BR0ICPEgSdbZZiS/yHf7Nvg4/GVaxP4tf+uanQ8s0u1TngfMde0ICPEgcxbJSXyq
fKD3aRxTvyJE8yiAWNE+XPhQEASWpDe5jS0ICPAg/YCswqWp163njkMsikbHFDCS
9Ev5oIvv1hPxa9OIX+kICPEgByeJhVdi0+m8Jxb/tHl3F7/rZ9KQuqDFQZuiTr70
5bwICPAgkniersWfZSMYFemEQWw6fsbkxj2eatWzXKZ6NzDJnyYICPEg8lLXm5pp
NEMV0ZvcE0yxX232gizWHQvXxWMIqTQ+EHIICPAgisTPBHQ0nVI4ftyiDktAJvCF
Qi/PWFOHikMOe5uOhW0ICPEgSuwpRsq6+B5ffXKwO8LpdkvLL50/R9P5rK5YKDak
OhYICAAFiJYNc9cZAQPkqibwEOi3GIDcjn0F0PajxFcklnwI8QReqLMp8AgLL9Ry
KZmzrgCD3+MNLvkMjikoaHR0cHM6Ly9maW5uZXkuY2FsZW5kYXIuZXRlcm5pdHl3
YWxsLmNvbQ==

My PGP key (will not be included in subsequent posts, except if/when updated)

A short selection of evidence that I have been claiming the same PGP key fingerprint (https://bitcointalk.org/index.php?topic=5225902.0) for a long time:

web.archive.org snapshot of my forum profile page, 2018-01-10 (https://web.archive.org/web/20180110235844/https://bitcointalk.org/index.php?action=profile;u=976210). Shows PGP fingerprint in the “other contact info” field (and also in my forum signature, though you need to disable CSS to see the truncated signature). https://archive.is/lqi7R is from 2018-01-02, and shows substantively the same information.
Archival snapshot 2017-12-26 of a post that I made 2017-12-25 (https://web.archive.org/web/20171226025059/https://bitcointalk.org/index.php?topic=2286988.60#msg26924143), showing PGP fingerprint in signature.
bitcoin-dev post 2017-12-25 re bech32 (https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-December/015477.html), showing my PGP fingerprint in my signature; compare this forum topic re bech32 (https://bitcointalk.org/index.php?topic=2646007.0), and this 2017-12-31 post on tor-dev re bech32 (https://lists.torproject.org/pipermail/tor-dev/2017-December/012743.html) (all with fingerprint in signature). Also compare with this 2017-12-21 post re bech32 (https://bitcointalk.org/index.php?topic=2624630.msg26747763#msg26747763) (archive 2017-12-23 (https://web.archive.org/web/20171223190705/https://bitcointalk.org/index.php?topic=2624630.0;all#msg26747763)), again with fingerprint in signature.

Code:

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on August 26, 2020, 12:37:46 AM

Editorial comment:

To test if anybody actually verifies, I am tempted to salt this with fake information—or perhaps to conceal herein the private keys for some Bitcoin. I fear that the latter would be safer than cold storage on an airgapped machine in a bunker beneath the Alps.

Nah.

Signing time: 2020-08-26 00:16:32

The timestamped file:

Code:

Code:

7283c172e8fe3f95f02c36623bab7813e9eaf005d12b235896cd8b4b6843a5f9

The OTS file (base64ed):

~~(The following will be edited when the “complete” OTS is available, following adequate confirmations on the Bitcoin blockchain.)~~

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIcoPBcuj+P5XwLDZiO6t4
E+nq8AXRKyNYls2LS2hDpfnwEN4kihI3v2E8JjCit2DBlIcI//AQDXDuDzvNMFjA
4MZkLLXMIwjxBF9FqhDwCJICV/aJAhVeAIPf4w0u+QyOIyJodHRwczovL2J0Yy5j
YWxlbmRhci5jYXRhbGxheHkuY29t//AQG838234MKMy/iauRmiaPngjwILKWZbJy
nmWBt8Q+12OIMT7NBbjUDJ7keVInLK9HA6WLCPEEX0WqEPAIPzB6Ybv3rqv/AIPf
4w0u+QyOKShodHRwczovL2Zpbm5leS5jYWxlbmRhci5ldGVybml0eXdhbGwuY29t
CPAgGVo99hRJZcz/6ZhaO3O817pRyIHdtIzv5ArWFHANoMAI8SDGYwCpQC/f323E
H/05+exNSM8qdOhAS8yCat3cQbJcTwjxIPBjlWL0amnBe6m/E4bxvXfI1xftOSGH
D+zCmC8XZtVICPEglQb8AKpIgtt/4tnMUajwQW8Tk3spn+tiU0AJ/g6zt+oI8SCO
sLbq0oNVL/471pjB70EQVcygqf9RPsT155dje2R9TwjwIAvUWJOWEzbTL5hVtqVy
594pqAcpUUlNWY6hxBbTg4UQCPEgV99WEmvUQ1bPuZ+q1w/TJtu/DJbhrvjxuyLn
KS2KawQI8SAIKcJmgs7L+jKY7tKELjY3LYAhrUy6ye2lvSybc5jf9gjwICOlWQ4h
mrpq68Vkyepydvl49W+2OF/2rG2fLjVZlePaCPAgMDqzRuI0yKHqHrBqUoy48N+I
MR9BpBUI78OrMqPrzr8I8SB7Wix8jjFPbdthPMCqV1FhMOJCXVkhOI9G9lR/Bfg3
tQjxIJWnccePjo5WILdKZn7zwMizuSmx4KGrgMCPTisuvP/ACPFZAQAAAAHkyxEF
IQEHW0N89cZa/lqfktOhYz6d1SAkvw0nDlBHQwAAAAAA/f///wIb8gUAAAAAABYA
FIsJsFh36ps4gAChC5rEMNZlcHqXAAAAAAAAAAAiaiDwBOPYCQAICPEg2gBkfEwZ
EVSCywf5tj8YWWvIfRu7KO6BeoVqBHdzkVwICPAgmcetiH/KOkou2HORy1bNGy0x
4Bky0uQwpFYmHj5gXukICPEgE23cCwtaowXFKGdGxFfXO9B5IyJ6/JP8t5ZkNe45
wMkICPEgEO/VR5FoearE6eaF9xHq6bBdiyiqTINAHgBESEWuttkICPAgOAqr/9at
TIrzU9RF2JLVZeA2t/UFpC07pOT7Jvo7KaYICPAgiyDHa7h7Cz9gn+k7CL3i4M1e
1cBwHGmnSZsVqp38rvsICPEgH+vjLO7MzJVXpBdT7je1ZCLMHI9QQYDU3GaeBzV5
BL4ICPAg2MWnxTrly7lgfe50gTkhswGU3mMxmNztUz9vzURzDk0ICPEgfXce3uSE
HqMdkQ+AIYCnfUTzyvYPhnaj4PvaDKOI3hkICPAgYV+cGWk/2DUuhN2aaWpV++bL
tkLO8KRp4LD4TV88GcgICPEge3R0HV9RYoA1Fw6J60qyUMj6QJxxZQc5vzOxOZAK
86oICPAg5utwyckbYGNLRdMAFgE+pnuxZ7f/eJn5IX02OyTNKdQICAAFiJYNc9cZ
AQPksSf/8BCyqQiz+WsQh0gHRWVFswJtCPEgvlfQA+TDMoWbW/t2BWB/XH61mlIy
TSWqEFzXsoM/6CQI8QRfRaoQ8AgV5+AppPGVIQCD3+MNLvkMjiwraHR0cHM6Ly9i
b2IuYnRjLmNhbGVuZGFyLm9wZW50aW1lc3RhbXBzLm9yZ/AQ6nc+B9YaeWuy6Lx8
6maz2AjwID/FLlGPK8f2H+17xtkyH9EcGRzKE2/TZakfVVn+lPMzCPEEX0WqEPAI
mppo+QGQu5cAg9/jDS75DI4uLWh0dHBzOi8vYWxpY2UuYnRjLmNhbGVuZGFyLm9w
ZW50aW1lc3RhbXBzLm9yZw==

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: Last of the V8s on August 26, 2020, 06:37:43 AM

Quote

gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: Signature made 08/26/20 01:16:32 GMT Summer Time
gpg: using EDDSA key 8D38C47CE08958A6BFC4179BC42793159F9EF949
gpg: Good signature from "Nullius <nullius@nym.zone>" [unknown]
gpg: aka "nullius <nullius@bitcult.faith>" [unknown]
gpg: aka "Bitcoin Forum uid 976210 (https://bitcointalk.org/)" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: C2E9 1CD7 4A4C 57A1 05F6 C21B 5A00 591B 2F30 7E0C
Subkey fingerprint: 8D38 C47C E089 58A6 BFC4 179B C427 9315 9F9E F949

Look what the cat dragged in. ;D

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: johhnyUA on September 24, 2020, 06:33:36 PM

Quote from: nullius on August 26, 2020, 12:37:46 AM

Nice to see you here again (only now i've found that you returned to this forum again).

https://i.imgur.com/YjnLzhA.png

About bitcoin keys is this joke or not, eh? :P Will try to recover it a little bit later.

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on September 25, 2020, 01:00:50 PM

Skip to the part that you should really want: Verification bits! (#post_september)

V8s: LOL. 😺

Thanks, johhny. I am not really back, or not supposed to be; it is why my activity is kind of all in one place lately...

Quote from: johhnyUA on September 24, 2020, 06:33:36 PM

About bitcoin keys is this joke or not, eh? :P Will try to recover it a little bit later.

Hah, made you look! Well, that was the point.

I said that I was tempted. If I really wanted to pay people to embrace cryptographic security, then—why, then I would spam a PGP 256% airdrop bounty signature campaign in the altcoin get-rich-quick forum (https://bitcointalk.org/index.php?topic=3107429.0)!

So, anyone else up for doing the most advanced, temporally enforced crypto-forum crypto-key stake yet invented?

Feedback would be good. How best could this work for you? I sort of still a little bit idealistically hope to eventually someday develop this concept into something that people actually use. Wow, such many qualifiers.

The timestamped file:

Code:

Code:

d3bb94baeb0e61b41db5e7fe5d66166d11311fa233da6e35b03c59dd2b9a4ba3

The OTS file (base64ed):

~~(The following will be edited when the “complete” OTS is available, following adequate confirmations on the Bitcoin blockchain.)~~

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEI07uUuusOYbQdtef+XWYW
bRExH6Iz2m41sDxZ3SuaS6PwEI0kN63afH8w7iIFA7XnszII8BAKGv1H3eJifgkR
8YEZaMRbCPAghFYOt3dSFXbSehFZ7GQlfAtCi4P/7/KG0oTSCJOZdigI8CBy+zSZ
WwI+JttTB3sLwi0yrlRxXu+k2XC5aSOgQcNNvgjxBF9t5rzwCFw8+nQwt77F/wCD
3+MNLvkMji4taHR0cHM6Ly9hbGljZS5idGMuY2FsZW5kYXIub3BlbnRpbWVzdGFt
cHMub3JnCPEgFwUtkLXfRlRViL3z5byvGCZM0pm6IRYEKGRVhTsKkusI8SAI2ZaH
DQz7gQTow3/5Iwu5AaH9vwB++JokivpIztdFTAjxIOHT+ZF+Wspo8YNeU4S7/Mn8
qH7RYW1CJROSRU4e9UYeCPAg1TTETCyqbbbYPxVTIeccP61ex6076slZq0nkwzyv
f4YI8SC6oUsPD3fYhcfRQ1Q9kFGxv4p7D4IPqdP1T/04+Dp/mAjxIL1K84zMoPoC
XJokFvLi9EJsF373JXYSV7xpVJjaWH6DCPAgdJjYngwNFQzerhFZVbCvVucjezlk
kdojkNSb77BbATcI8SCuvLq69huLDAGH+v9rJ/zsG9ovjn0e48M344ZxCSNkiQjx
IHJyQCtb5cYjFaPKypF7/mE+2xjYwwLt3NklZ6ix52SMCPEg9wFHKVwXUFQ9qPVj
JUD8GOZZ7ieWEpcuc71jMDqIZdII8CCnGlCN0f1X+LfalQlSkMkEnBer8F55ocpr
g68NdTZHaAjxWQEAAAAB/2w4pbpp/fV2k8XpvJwJGtJ4urZJC7ukc3Lyzldc7oYA
AAAAAP3///8C6LUjAAAAAAAWABREiM2jckBAuL5RzSlJW+tX2awFwAAAAAAAAAAA
Imog8ATN6gkACAjxIBK0MrP8jQgZgPQo1kIGPn/F5wAqiTo3Rb7slP93d687CAjw
INeWD46d5CXxeBKixVGws/WNu9BACTWRz1AW0xy+TsocCAjxIOtT/29oKV9LXEMs
iC/ZAWu6qqQnHY1X68gEJpXa2JKOCAjwIC6UuMEQNfnQ8bGvd7eyOBsSu9VqNvkk
tze2a6gjmsPBCAjxIFIOZgLH7Un2arLGd2yuiHJ7908PQMxYYhbG/sk4PwloCAjw
IEqZcFC/3Bt44D32Bo61qLtApNi64iCtG4JPP0oQmMhICAjwIBfYq0GvAi2g03kU
xVV2s47ptx3iSIWteICkRh98+5IwCAjwIOczvomRmb1Kufu+fIW3ARA3nArxYRAQ
QMyLVvhc7UQmCAjwIBya6jc/o/IEU5+8Tdo4xzl4EGUIhMAk1Nm6bRgr6f+RCAjw
IDBIKGZa+hA2tsCuP1DW3p1eHyn9590eu4ckTqttgUM5CAjwIM0t+3xI2LwlYMno
vPOTyeKjLQzbCk+fAP5nuQk3D03VCAjxIGNxphULx048z/KFzADZfLdeowOscOyQ
vXvivs/msoOfCAgABYiWDXPXGQEDztUn

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on October 25, 2020, 05:58:03 PM

The timestamped file:

N.b., the signing time was 2020-10-24 22:51:37 UTC. I just waited for the timestamp to get confirmations, this time around; then, I forgot to post it. Why bother making another one.

Code:

Code:

5be1da1618b445496b2877b17719656c64c7cb2dfc46c49aca1ffec31a2c3327

The OTS file (base64ed):

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIW+HaFhi0RUlrKHexdxll
bGTHyy38RsSayh/+wxosMyfwEEHINWtnGFHnCBK/fjGqXc8I8BCXjYsrxKV8208J
S4PVexjsCPEEX5SwRPAICekAQjLdMsb/AIPf4w0u+QyOLi1odHRwczovL2FsaWNl
LmJ0Yy5jYWxlbmRhci5vcGVudGltZXN0YW1wcy5vcmcI8CCm6+5+ZqoJZsL9z2iK
hdHvAiVWtTGaOAOw4qT+HRKXFgjwIMhUBD7D8QCLgWUS4V155n5FSfm7bmzYP/My
rLJN0cZXCPEgBdv07ILXaPnXYznLAoKH5vCTRyBQgN8o0MOOf2UcrLEI8CBe64ER
cxxw2IqPJs2W+JqsPt6wdoxkXSrlMrgWHLyrLgjwIDK8MOkY1ui134NMhTuK28wC
yTvu9rLYDHc9IzOLn6lJCPEgcW4+XLeuqb8GAXL8sQiVsYsATyWBmtSbx/5UqiVp
svQI8SAx4ZMp1ksUqfDQJ7WKVW5KgrXVO9hj2jgGoJ8tqcGzOAjxIPWu8HRdOTct
DlAzMr+oEwQFoF85iwt2o7fzTUoZBC1GCPAgGFoh2i3GjNGg/vJMrh4AxmyF04El
9ZI/GqB270HO82gI8SD0Li3/xf7kd5rfM4f+XHdRkI5R7uqEVM7vwFekp2260wjw
IHfGzL/1/4Xqr9zbIufZM3eGLGgZm21gAq07FM3iaAzGCPFZAQAAAAGPY2nj3tIE
pLOA1N0vJYv1BVNN4TKySyExNxJjgv1iFgAAAAAA/f///wLiPBoAAAAAABYAFHAK
sEMrMhuA4Xc7X0To5veiO8ZwAAAAAAAAAAAiaiDwBF77CQAICPAgt1/bO0wmeSkd
zA37R9KxjnK4LgAeLPFhsmS63Iwx8hQICPAgS9cl+shB0M391UaGEXOS4YS+dZpd
i6U1d1H3W2DwW5EICPAgU1dKbL59pdPyK5NCIkcr4mRRJ6XaONawZ1wZNsXyk7MI
CPAge28vMDYpEMoJYEfMjdr2AW5Ozh8Aqoiz34pGJcJWfUgICPAgDLjhHCe99Xkd
7RDwypr1CdkKNr0wCSQAaKG5wTDfkcQICPAgdBV0sSsJ2Xyesvkqm+xvjexbkHuB
DQdhO98WFFGYBR0ICPEgTZSMSgzj3Fy9jMNuWlETF5QTXHHoBshJ2UIdjPGnfjAI
CPEg7GSSaOmzJU8ZT10PLE2gsLLpBoTdpFPYJtWR74GeoT4ICPAghoJcFzg5HXsk
cuYoYVgDY4LBl6cFb3nMiEc+0C+gv4UICPAgiioQNI34xuDj70h5FoJgxknyIiiJ
jgk0LGaXf19shloICPAgIGMw6zG3TdmiMcA6Kb+fBXm2l6JI3Uio9LoGpt9fXYEI
CPEgJiQ9bUMgdq6D3yDP7wuNtyHISveQ9KDYU61ZyEa1SJ0ICAAFiJYNc9cZAQPf
9ic=

Title: Re: Nullian Verification: Post your PGP keys and timestamped statements here!
Post by: nullius on November 25, 2020, 07:25:31 PM

PSA: Use crypto!

Please help to support this timestamp server’s trustless blockchain timestamping. (It is not mine; I do not benefit from this!)

Quote from: https://alice.btc.calendar.opentimestamps.org/

This is an OpenTimestamps (https://opentimestamps.org/) Calendar Server (https://github.com/opentimestamps/opentimestamps-server) (v0.5.0)

Pending commitments: 21
Transactions waiting for confirmation: 1
Most recent unconfirmed timestamp tx: None (0 prior versions)
Most recent merkle tree tip: None
Best-block: 0000000000000000000a7ab152e6f454737d5f84dc95de809a44fa31e480f207, height 658644

Wallet balance: 0.02506021 BTC

You can donate to the wallet by sending funds to:
https://i.imgur.com/OYiGLdT.png
bc1q2fl3ux03qyng39mx8d0dxc3jrsv5kl3d8q5mw5

Average time between transactions in the last week: 2.71 hours
Fees used in the last week: 0.00107453 BTC

Latest mined transactions (confirmations):

a3fa8c9c7d52302a93c19f4c4c3b1aac2f9d548c0eb8d674ea90fa378d40d3b2 (1) [...]

See also Bob (https://bob.btc.calendar.opentimestamps.org/), Finney (https://finney.calendar.eternitywall.com/), and Catallaxy (https://ots.btc.catallaxy.com/).

2020-11-25: The timestamped file:

Code:

Code:

a49f344012a5ebfcd493fa71ca14444515a3c9e99ffd3499bffa1e108f4d7f3d

The OTS file (base64ed):

~~(The following will be edited when the “complete” OTS is available, following adequate confirmations on the Bitcoin blockchain.)~~

Code:

AE9wZW5UaW1lc3RhbXBzAABQcm9vZgC/ieLohOiSlAEIpJ80QBKl6/zUk/pxyhRE
RRWjyemf/TSZv/oeEI9Nfz3wEKsqpfYKFfJWKB0YPrYwHTsI8BCs0o/qjplXZHQk
6ciZ19d3CPEEX76qyfAInjghAH5BYQj/AIPf4w0u+QyOLi1odHRwczovL2FsaWNl
LmJ0Yy5jYWxlbmRhci5vcGVudGltZXN0YW1wcy5vcmcI8CAaABRtx0Ge+AUOAelu
Si8zRWtArt9JZfPAwC21dXwWDwjwIEoDg1TNVG3rFutIXORs0L80MXcwyMAbqH9/
fuTm7u8yCPAgP1lRYyLTpwAzV3hZ+X9pt7QJtrQTS8VDAur7PWxIPQAI8CD/bwEo
3uQdgV/+EO+h//SAkQ6DLSlcBysPzNAPa3HxYwjxIJ6qp9zOIhZpNjafBs9nnt/6
z4R1JGctv6fSO6fQCBUCCPAgTWwpLPsinuCZ/UYGmGcpd8gCQZ1OedlCaja3Jhw3
wbMI8SDuq5Q7zul3RaiT1WxCNdScf/p9PmGenZOxUNRw47/FrwjxINbBy9i+HByW
RewD9Q5Bp7iN2vOti0JtCOumFPcKcxqxCPEgTonUAFlrykcE8sqMKeiLIIvp9an2
fTlYq2W916K7tSMI8SB757P4/CZoSkz3UmcrxwabMExxVvjdvFIodkDz8zQOlQjx
IJBuYH8+y+H5ehN+TSUXwchGhRCZVBDK64bhTmCgC7aCCPFZAQAAAAG7Wbz9eta/
R/7UUm9PUTr61Cd8SGGnwQdsueEVbISESgAAAAAA/f///wIrDBMAAAAAABYAFKqS
gvdDZ4mqOufgq78cWtSweVIHAAAAAAAAAAAiaiDwBNMMCgAICPEgMeOOudT9s2+I
d3Zo0rMBCwy0wSChi5bqAoabW+OTdvQICPAgmfLv1tCOLjRSMQKrKo4azqXCgWXQ
R9Do//TWbDaPEIYICPAgiArspIaanRxb2whPnQB4Ameglj1SVnt0rOtzOCiVeOII
CPAgaYvSK4pjoL272uyRUpO/e03qz1pqcytdWTocn1MDICsICPEgai9A6kHBYSLL
XPWVyRMHdzbAiKTcjg9LHROaUN2MqCwICPAgUK9F3Rw6vXTNyvkadUuJklKAArj8
sgDks4Wl1CknMSwICPEgFB1SXpWv0fuh79o/Sji+h32f8SIpFiJwC3dYo8JjS3gI
CPEglhbhNNymgWHj8VUilvbliD4897DaQvYGxoOhM+WE6ykICPAg29QcyUuY6/oI
AR2QMhp1HonsgVVe/qBTnLgd6WQxs0EICPAgIT2GGqSnkMv+KlDIWz6qu1NEa2p/
IKcNDaeMQ2feU9EICPAg5pcJh2GUQcGG4TBKTzhLuGVMpwwEQlpND65rA5w525MI
CPAg4lXLf6DQcneY5zgQw8r9VMK6F6Ff3EULMbGOYWRnPp4ICAAFiJYNc9cZAQPU
mSg=

Bitcoin Forum

Economy => Reputation => Topic started by: nullius on March 15, 2020, 10:04:06 PM