709 entries in 0.805s
mircea_popescu: punkman see your pms, apparently ppl can't go from
deeds to privkey ?
punkbot: nubbins`: No valid
deeds found, try again.
nubbins`: ;;later tell punkman plz to provide complete pseudocode for
deeds nubbins`: anyway. does anyone know how the fuck
deeds generates these brainwallet passphrases? :D
assbot: Logged on 26-10-2014 20:32:15; punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key
nubbins`: mircea_popescu according to
deeds.bitcoin-assets.com i'm supposed to end up with the brainwallet passphrase "BXZKQx2iLYyRpUCmdWCqJBvgUdvqWH4EE8TV1ns3pxLZ"
assbot: Logged on 26-10-2014 20:32:15; punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key
assbot: Logged on 26-10-2014 20:32:15; punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key
mircea_popescu: decimation all submitted
deeds during one hour go in the same bundle./
decimation: one would imagine that keeping the pile of all past
deeds would become cumbersome
jurov: no there are only
deeds jurov: only benefit is possiblity to (pruportedly) multiple versions of one bundle with perviously unknowns
deeds to appear
jurov: punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key << ever heard of hash extension attack?
decimation: so in your blob you put the chronological list of hashes for all
deeds - user will be able to confirm that this blob was indeed put into the blockchain by deedbot
decimation: so if I'm reading that correctly, the list of sha256 hashes of all the
deeds would allow one to 'detect
deeds'
assbot: Logged on 26-10-2014 20:32:15; punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key
TheNewDeal: it's basically a blockchain parser that just filters for
deeds, no?
jurov: ha. poor qntra writer
deeds will contain clause like "receiver is responsible for identifying any circumstances that may render this agreement void and act accordingly"
Apocalyptic: just noticed that all
deeds processed by deadbot are SHA1-hashed so far
kakobrekla: <mircea_popescu> did kakobrekla delegate
deeds.bitcoin-assets.com jetzt ? < it works, no?
mircea_popescu: did kakobrekla delegate
deeds.bitcoin-assets.com jetzt ?
mircea_popescu: asciilifeform nah original spec called for keeping all the
deeds, as a sort of primitive distributed backup
punkman:
deeds are sha256 hashed, hash is b58encoded, b58encoded hashes of all
deeds are joined with ",", that string is sha256'd again and that's the private key
☟︎ punkbot: punkman: No pending
deeds | Last bundle 2 hours, 55 minutes, and 50 seconds ago
punkman: jurov: will make a standalone verifier for
deeds punkbot: punkman: No pending
deeds | Last bundle 6 minutes and 54 seconds ago | 1 unconfirmed bundle
punkbot: punkman: No pending
deeds | Last bundle n/a ago
punkman: but other
deeds might have html
decimation: "with paper money he could buy a lot of the
deeds needed to back up the words. With paper money he could persuade the Sirian foe to kick himself good and hard in the pants and save the Terrans a tedious chore"
mircea_popescu: i know. but i mean, issue it in his name/gpg key, and require that in order for a third party to benefit, there must be a
deeds registered, signed assignation
mircea_popescu: not to mention it motivates him to finish the
deeds thing already :D
RagnarDanneskjol: I wouldnt do any
deeds at this point. I believe he is resetting a lot of things
kakobrekla: 2 suggestions: make
deeds searchable and add a simple syntax, at least so that we specify 'title' and 'content' in the signed content
mircea_popescu: and the website moved over to
deeds.ba and the key process fixed. there's a list.
punkman: BingoBoingo: what's with your bogus
deeds nubbins`: how is this different from just registering a few different
deeds?
nubbins`: a nice companion tool on the
deeds website would be a small form w/ textbox and button where one can generate pub/priv keys by the same method
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (1
deeds 1371 bytes in next bundle)
RagnarDanneskjol: oh -i miscounted a decimal spot - guess ther's enough for 20
deeds left
RagnarDanneskjol: jurov, do you mind throwing a few bitcents in there.. it only has enough for a couple of
deeds left
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (1
deeds 1371 bytes in next bundle)
RagnarDanneskjol: as for immediate publishing - I am all in favor of immediacy. believe the idea was bundling multiple
deeds over an hour into a single tx was more efficient, etc
RagnarDanneskjol: the cost of deed is a fe cents, so believe the idea was to have someone throw a bitcoin in there and have enough to cover all
deeds for a year
jurov: RagnarDanneskjol: i suggest immediate publishing of
deeds as paid service
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending
deeds.)
deedBot: DEEDBOT_CHAN=#bitcoin-assets ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending
deeds.)
mircea_popescu: ;;later tell MolokoDesk aite once you wake up, kako's going to set you up with a
deeds.bitcoin-assets.com zone and a server login. an wipe the test bundles when you do it too.
mircea_popescu: MolokoDesk aite once you wake up, kako's going to set you up with a
deeds.bitcoin-assets.com zone and a server login.
deedBot: DEEDBOT_CHAN=#cex-squawk ERROR_CHAN=MolokoDesk INTERVAL=3600 (2
deeds 1201 bytes in next bundle)
deedBot: DEEDBOT_CHAN=#cex-squawk ERROR_CHAN=MolokoDesk INTERVAL=3600 (no pending
deeds.)