79b79aa8

Joined Apr 22, 2018

Mute
1FDKNY76SZGY4wa43Tg65BqKA5iLnh1JiN
Actions 1,265
Following 88
Followers 29
Topics following 23
Muted 0
Is Muted By 0

replied 2025d
Sk8eM dUb
f6 - h5
replied 2025d
Sk8eM dUb
d6 - e5
replied 2025d
Sk8eM dUb
d7 - e5
replied 2025d
anarchovegan
i'm staying put
replied 2026d
it would be a nice gesture for miners using the BU client to start BIP135 signalling.
replied 2026d
Sk8eM dUb
f8 - d6
replied 2027d
in this respect, bitcoin is no worse than the current monetary system. or tell me you understand that fully and could help explain it to a randomly chosen person.
replied 2027d
all in all: is your memo legacy important enough for one of your sons to potentially have to go look it up in the dead chain repo?
replied 2027d
anarchovegan
will you know what / when to buy back?
replied 2027d
Sk8eM dUb
b8 - d7
replied 2028d
Sk8eM dUb
e7 - e6
2029d · memochicken
with tips?
replied 2034d
BitcoinHoarder
yes, that was a misunderstanding. i thought we were using nov. 1 to test Collect and its ongoing infrastructure work.
replied 2034d
BitcoinHoarder
how much were you going to spend? also, people have been donating to Collect, under the understanding that those funds would be used on nov. 1 test, no?
replied 2034d
Sk8eM dUb
g8 - f6
replied 2034d
Sk8eM dUb
d7 - d5
replied 2034d
Sk8eM dUb
never! looks really difficult. i should try it though.
replied 2034d
thoughts?
replied 2034d
minimum objectives of test: (a) make sure bot works as expected when funds are unlocked (b) gain experience in securely handling funds (c) establish how many txns/min bot sends
replied 2034d
(4) amount to be spent on nov.1 test remains TBD.
2034d · txBlasterCollect
let's review. (1) we agreed to test the Collect bot on nov 1. (2) the bot appears to work well and is accruing BCH. (3) funds need to be moved to a multisig address for security.
2034d · stresstestbitcoin.cash
10 days to Nov. 1 (tentative date for testing the Collect bot). more info on the txBlasterCollect topic.
replied 2034d
Sk8eM dUb
i set up a real board and left it on the table . . . that was fun.
replied 2034d
ideal would be to share pubkey privately. but as this multisig is only precautionary measure and not meant to be foolproof we could move forward as agreed.
replied 2034d
this was exactly the plan but can't even get past sharing the pubkey (we're only in touch via memo). the point is not to make it foolproof, but to alleviate the bot writer's risk.