8100+ entries in 0.614s
assbot: [MPEX] [S.MPOE] 32400 @ 0.00041934 = 13.5866 BTC [-] {
2}
thestringpuller: ah. yea. I'm running on debian jessie a core
2 duo machine (older but not super old). but everytime thing gets "up to date" it stops asking for blocks
assbot: [MPEX] [S.MPOE] 14150 @ 0.0004203 = 5.9472 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 22176 @ 0.00042138 = 9.3445 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 16300 @ 0.00042066 = 6.8568 BTC [+] {
2}
mircea_popescu: to summarize said argument attempts : line 1. "high voltage is dangerous" "mkay, throw out your tv" ; line
2 : "you will have to protect the line" "yes you will" ; line 3 : "this was done historically" "yes it was".
mircea_popescu: and
2. IF you want to argue against something i said, do yourself the favour and BRING VERY GOOD ARGUMENTS. because your own personal word will count for nothing much, and you'll just make a clown out of yourself.
solrodar: I have only 0.
2 BTC of outstanding bets, so this isn't really a conflict of interest for me
gribble: Bitstamp BTCUSD last: 413.78, vol: 3292.33562821 | BTC-E BTCUSD last: 414.281, vol: 5136.5319 | Bitfinex BTCUSD last: 413.47, vol: 9471.992610630001 | CampBX BTCUSD last: 420.
2, vol: 1.68670123 | BTCChina BTCUSD last: 417.492968, vol: 32362.02050000 | Kraken BTCUSD last: 415.157, vol: 2359.4455159 | Bitcoin-Central BTCUSD last: 417.5235, vol: 63.25511783 | Volume-weighted last average: (1 more message)
assbot: [MPEX] [S.MPOE] 11200 @ 0.00041975 = 4.7012 BTC [-] {
2}
mircea_popescu: ben_vulpes a simple way to address the problem is put in a fixed per-bet fee, of say .
2 or .3 or w/e, and make bet minimum 1 or somesuch.
assbot: [MPEX] [S.MPOE] 32201 @ 0.00041993 = 13.5222 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 5697 @ 0.00041994 =
2.3924 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 15800 @ 0.00042133 = 6.657 BTC [+] {
2}
danielpbarron: how do you get to 1 from a shift of
2 away from 7?
mircea_popescu: this because
2 bits =
2^
2 = 4. had the shift been 17 bits, then you'd get to do
2^17 = 131072 old style hashings for each new style digest you calculate.
mircea_popescu: hash2 would have been the same for all nonces over 3, ie, 4, 5, 6 and 7. it'd have also been the same for all nonces under 4, ie, 0, 1,
2 and 3.
mircea_popescu: if in fact a shift by
2 was in effect, it'd be the case that hash1=f(header+7) and hash2 = g(digest(1)+1)
assbot: Logged on 17-03-2016 14:26:26; mircea_popescu:
http://log.bitcoin-assets.com/?date=17-03-2016#1435048 << if the nonce is not shifted at all, each digest is good for exactly one nonce. if the nonce is shifted one bit, each digest is good for
2 nonces. if it is shifted 10 bits, 1024 nonces. etc.
assbot: Logged on 17-03-2016 03:14:29; asciilifeform: that makes ...
2? 3? usg-authored corpses in the case now ?
davout: that would be three-fold: not charge more than a few percent for the whole liquidation, evaluate all claims against bitbet in light of its actual contract (and more specifically, the 3.
2 (d) clause), try to get as much as possible from the non-cash assets, and (quite importantly) not disappear with the cash
assbot: [MPEX] [S.MPOE] 32574 @ 0.00042099 = 13.7133 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 5900 @ 0.00041975 =
2.4765 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 20000 @ 0.00042133 = 8.4266 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 30592 @ 0.00041989 = 12.8453 BTC [-] {
2}
mod6: I'd even be open to the idea of two people splitting up the work there. Say, split 2BTC/yr between
2 individuals so that we get good coverage at all times.
mod6: well, no one said you were gonna live off of
2 BTC a year, unless you live on the dock and eat fish-heads for dinner every night.
mod6: dare i say, that I would lay out 10 BTC,
2 BTC per year for someone to handle this task.
mircea_popescu: knob 1 above decides whether to obsolete current miners entirely or just partially, and is a [true] soft vs hard fork ; knob
2 decides how much i/o pressure to put on relay nodes ; knob 3 decides how much relay work to require in the mix.
mircea_popescu: BOTH hash 1 and hash
2 have to be under a number to qualify as a found block.
mircea_popescu: in the proposed model : a header is calculated, same way. to this, anonce is added, the combine hashed. this is hash 1. a digest is calculated, on the basis of past blocks. to this, the SAME nonce is added. the combine hashed. this is hash
2 assbot: [MPEX] [S.MPOE] 21350 @ 0.00042004 = 8.9679 BTC [-] {
2}
mircea_popescu: but look at the jump : 1) unexplained item can be explained by a or b ;
2) it's a b-olympics!
mircea_popescu:
2) IF miners come out with their own fork, what do we do ?
assbot: Logged on 16-03-2016 02:56:58; phf: trinque: as per that rant only things needing pressing are asciilifeform_shiva_part_1_of_2, asciilifeform_shiva_part_2_of_2 and asciilifeform_shiva_fix_flag_bug
assbot: Logged on 16-03-2016 01:55:56; mircea_popescu: trinque iirc the bitcoin-derived one had two parts named 1 and
2 which you both need
phf: trinque: as per that rant only things needing pressing are asciilifeform_shiva_part_1_of_2, asciilifeform_shiva_part_2_of_2 and asciilifeform_shiva_fix_flag_bug
☟︎ mircea_popescu: trinque iirc the bitcoin-derived one had two parts named 1 and
2 which you both need
☟︎ assbot: [MPEX] [S.MPOE] 63700 @ 0.00042051 = 26.7865 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 18800 @ 0.00042501 = 7.9902 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 39350 @ 0.00042501 = 16.7241 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 27000 @ 0.00042602 = 11.5025 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 11950 @ 0.00042318 = 5.057 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 48611 @ 0.00042183 = 20.5056 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 12037 @ 0.00042275 = 5.0886 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 39165 @ 0.0004228 = 16.559 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 18451 @ 0.00042327 = 7.8098 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 47700 @ 0.00042549 = 20.2959 BTC [+] {
2}
solrodar: for complete closure, 10 BTC,
2 months
assbot: [MPEX] [S.MPOE] 17800 @ 0.00042487 = 7.5627 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 45813 @ 0.00042487 = 19.4646 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 60050 @ 0.00042674 = 25.6257 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 20900 @ 0.00042584 = 8.9001 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 45300 @ 0.0004228 = 19.1528 BTC [-] {
2}
jurov: phf well.. such magnitude of payouts is fine for coinbr where i'm alone.. not for
2 owners, shareholders, referees,...
assbot: [MPEX] [S.MPOE] 56689 @ 0.00042637 = 24.1705 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 17165 @ 0.00042894 = 7.3628 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 58500 @ 0.00042572 = 24.9046 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 28962 @ 0.00042657 = 12.3543 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 94145 @ 0.00042716 = 40.215 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 104870 @ 0.00042765 = 44.8477 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 12000 @ 0.00042716 = 5.1259 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 44950 @ 0.00043125 = 19.3847 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 26302 @ 0.0004313 = 11.3441 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 93550 @ 0.00043262 = 40.4716 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 57200 @ 0.00043122 = 24.6658 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 43139 @ 0.00043182 = 18.6283 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 48226 @ 0.00043232 = 20.8491 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 85309 @ 0.00043847 = 37.4054 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 33400 @ 0.00043925 = 14.671 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 69484 @ 0.00043844 = 30.4646 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 85071 @ 0.00044016 = 37.4449 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 5200 @ 0.0004437 =
2.3072 BTC [+]
assbot: [MPEX] [S.MPOE] 109223 @ 0.00044088 = 48.1542 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 57067 @ 0.00044414 = 25.3457 BTC [+] {
2}
assbot: [MPEX] [S.MPOE] 41184 @ 0.00044016 = 18.1275 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 50448 @ 0.00044269 = 22.3328 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 68650 @ 0.0004427 = 30.3914 BTC [-] {
2}
assbot: [MPEX] [S.MPOE] 51328 @ 0.00049322 = 25.316 BTC [-] {
2}