254 entries in 0.582s
mircea_popescu: Short Term Steps Use the Intel and ARM optimized
SHA256 routines, which increase
SHA256 speed by about 80%. << NO.
punkman: I think you just gotta
SHA256 the deed bundle and use that as the private exponent
trinque: Hasimir: deedbot records the
sha256 of gpg signed messages into the bitcoin blockchain
mike_c: comodo
sha256 cert good through 11/15
mod6: yep, got that too... but check the
sha256's of the dl'd patch files, see if they match the checksums that the ml inserted into the file name.
mod6: <+ascii_field> the patch, note, did not remove all (there is a 'what is my ip' thing in there ) << ah, i recall. ok and this is what initiated the conversation about
SHA256 addy's as opposd to dotted quads right?
felipelalli: ok, I'll try: I'd like to use OTC as a global "blacklist". But it is bad for that because a scammer won't create an account on OTC, or if his reputation is bad, he'll erase it. So we could create a "standard" like for example: br-8d255152 where "br" is the country code ISO and 8d255152 is the first 8 chars of
SHA256 of user country document (in Brazil we call CPF and in Australia ID)
Adlai: doesn't reduce the total number, but fuck using decimal for
sha256 trinque: pub/priv-key encrypt either works or doesn't,
sha256 either works or doesn't
danielpbarron: Add FingerprintHash option to ssh(1) and sshd(8), and equivalent command-line flags to the other tools to control algorithm used for key fingerprints. The default changes from MD5 to
SHA256 and format from hex to base64.
kakobrekla: jurov for otp?
sha256 of a paragraph i made up from non-dict words plus some pseudo random bs that changes each run
davout: you can just
sha256 your content, make an address out of that, send a bitcent there, and since that's how deedbot is supposed to work, you get your stuff deedbot-timestamped before deedbot even exists
davout: just
sha256 it and send that to the bot
decimation: asciilifeform: mircea_popescu: re: deterministic wallets << the ware that someone dropped in the chan a few days ago was amusing: you enter you die rolls on the command line (history!) and then it converts to 'diceware' string, and then it takes a
sha256 hash
cazalla: anyway, his timeline is still fucked up, bitmain didn't even ship scrpt miners back in october nor can you mine scypt coins with
sha256 asics despite him claiming otherwise
jurov:
sha256(ip) alone can be bruteforced easily
punkman1: nubbins`:
sha256 of raw genesis deed is 9c68d5c322a3f4212112c5eb1a68dffdb49d105c34256bf219581da524c90522
assbot: Logged on 28-10-2014 06:51:56; punkman: if you base58decode the deed hash, you get a
sha256 hash of raw deed
punkman: if you base58decode the deed hash, you get a
sha256 hash of raw deed
punkman: just
sha256 the BXZ... string
punkman:
sha256 of bundle: 07014e56d4c34fb7962db64e2cdf5ebcd3f8eca891a0ea697cc5f46f55d1da9d
BingoBoingo:
sha256 of my guess on which trilema url hanbot wrote about 86e9f3b06d8abfde4f1323725907a4c9ccb6017d7ec35250f63ba735b6edbd08
nubbins`: var hash = Crypto.
SHA256($('#pass').val(), { asBytes: true });
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
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
jurov: bitcoin solves it by using double
sha256, otherwise it's solved by using HMAC
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 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
assbot: Logged on 16-10-2014 14:00:51; mircea_popescu: btw, cazalla bingoboingo and everyone else in the same situation : if the blob gpg spits out when you sign contains a SHA1 you are using the older, and perhaps not all that secure digest algo. you should move on to sha512 either with --digest-algo SHA512 or else edit gpg.conf to insert personal-digest-preferences SHA512 SHA384
SHA256 Apocalyptic: by the way are SHA1 gpg-signed messages considered read ? I read somewhere one might rather use
sha256 or higher, don't know if there's any merit to that claim
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
☟︎ punkman: so if someone wants to do some independent verification, hash "BXZKQx2iLYyRpUCmdWCqJBvgUdvqWH4EE8TV1ns3pxLZ" with
sha256, convert to big int, make Bitcoin private key with big int, verify the key's address is 149LB8VYaT1BdMLyQUL92Kj6KrJfNwcp64.
jurov: cut -d ' ' -f 3- bitcoin-0.5.3-no-crud.
sha256.manifest does
mircea_popescu: btw, cazalla bingoboingo and everyone else in the same situation : if the blob gpg spits out when you sign contains a SHA1 you are using the older, and perhaps not all that secure digest algo. you should move on to sha512 either with --digest-algo SHA512 or else edit gpg.conf to insert personal-digest-preferences SHA512 SHA384
SHA256 ☟︎☟︎ punkman: for existing deedbot, the whole bundle goes through
sha256, then that hash is manipulated to create a public address
MolokoDesk: the hashing spec is just
SHA256 of the file converted to a bitcoin address.
MolokoDeck: bot sits in here. People point it at a cryptocontract with multiple signatories. it verifies the signatures. if they're good it creates an unspendable bitcoin transaction with the address encoding the
SHA256 hash of the contract. When that transaction clears and is on the blockchain, it notifies the IRC channel and gives the URL of a logged copy of the document, it's associated hash, and a pointer to the blockchain transac
MolokoDeck: then the bot would return an
SHA256 hash of the document, encode it as a bitcoin address and make a minimum non-spendable transaction, and log to a repository or blog the document with the
sha256 hash and the transaction ID containing the encoded hash, and the block number it's in. It would wait to get a confirmation before doing this so the transaction would be in the blockchain.
MolokoDeck: I'm not sure there's a quantum algorith for
SHA256 that's particularly leveraged, but there are supposedly turing-complete quantum gate computers that could accellerate that. Let's not go into that.
mike_c: depositor insurance: the insurer publishes a list like this: coinbr insured accounts -
sha256(act_id): amount,
sha256(act_id): amount
mircea_popescu: decimation here's more. sha1 is implemented as "sha1sum".
sha256 however is implemented as "
sha256". then sha512 is... "sha512sum"
assbot: [
SHA256] Altcoin | Page 22 | Bitcointa.lk
BayAreaCoins: I'm more interested in the mining power behind it and the networks on going security. Total supply : * 2734040 HUC Hashrate : *
sha256 : 2 818.74TH/s * scrypt : 13.30GH/s
jurov: Crypto.
SHA256(window.screen.height, window.screen.width, window.screen.colorDepth, window.screen.availHeight, window.screen.availWidth, window.screen.pixelDepth, date, timeZoneOffset, navigator.userAgent, all browser plugins, all mime types of the browser, cookies, language, browser history, browser url) to xor that in to the random bytes.
mircea_popescu: The header is signed with the coinbase transaction's private key, and the hash (
SHA256(SIG(header, privkey))) of that signature is smaller than a second difficulty parameter Y.
punkman: yo dawg I heard u like difficulty: "The header is signed with the coinbase transaction's private key, and the hash (
SHA256(SIG(header, privkey))) of that signature is smaller than a second difficulty parameter Y. "
pankkake:
sha256, and everything the same as Bitcoin
mircea_popescu: remind me, what are the chain characteristics ?
sha256 ? how many per block, how frequent blocks ?
Naphex: so.. if the difficulty adjusts itself to do
sha256 for 10 minutes, isn't bitcoin backed by TIME?
Vexual: u tink someone clever will make a
sha256 chip to end the game ascii?
punkman: no idea, they have
sha256 though
ozbot: [
SHA256] Altcoin | Page 22 | Bitcointa.lk
mircea_popescu: fluffypony: is there a firm love for
sha256 as an algo? << 512.
fluffypony: is there a firm love for
sha256 as an algo?
Naphex: signature is hmac-
sha256 with secret, from field 1 to uuid
artifexd: I imagine it would work with any
sha256 coin.
ozbot: [
SHA256] Altcoin | Bitcointa.lk
fluffypony: rithm: I think I'm going to try random
sha256 hash collision instead
tg2: I stand by my analysis though that it won't be near as prolific as
sha256 tg2: Vs 1000x more with
sha256 asics
Ademan: asciilifeform: RAM for what?
SHA256 doesn't need much memory
mike_c: how the fuck is anyone supposed to find a
sha256 hash with 16 leading zeros? bitcoin mining is absurd.