Search content
Sort by
Showing 20 of 34 results by fusion7
Hi
It's a compile issue on mingw.
Remove pthread_t definition and replace it with diffs in this commit.
https://github.com/laanwj/bitcoin/commit/61d85071405b99c3734606eed31ea8f615c0c77a
src/util.cpp and src/util.h
13G3U4vXLGYYomw29yfV7Uj6xpWLd52RoR
Thanks
It's a compile issue on mingw.
Remove pthread_t definition and replace it with diffs in this commit.
https://github.com/laanwj/bitcoin/commit/61d85071405b99c3734606eed31ea8f615c0c77a
src/util.cpp and src/util.h
13G3U4vXLGYYomw29yfV7Uj6xpWLd52RoR
Thanks
In either case it's not enough to break SHA256, it's also needed to break RIPEMD160 and ECDSA.
You could "just" break RIPEMD-160 & SHA-256 OR ECDSA (limited to addresses where the PubKey is known).
Find a PubKeyB such that for an existing PubKey A they both produce the same PubKeyHash.
i.e.
RIPEMD-160(SHA-256(SHA-256(PubKeyA)) == PubKeyHashA
RIPEMD-160(SHA-256(SHA-256(PubKeyB)) == PubKeyHashB
If PubKeyHashA == PubKeyHashB then the private key for either PubKeyA or PubKeyB can spend coins sent to Address A or B even if PubKeyA =/= PubKeyB.
Remember in a normal Bitcoin tx you are not paying to the PubKey you are paying to the hash of the PubKey.
1. How do you get Private Key B that's needed to sign the transaction?
2. Isn't address generation RIPEMD-160(SHA-256(PubKey)) rather than RIPEMD-160(SHA-256(SHA-256(PubKey))?
Re: [OPEN] Bitmine CoinCraft 28nm chip distribution (December W50, 42.5BTC/THps)
I have a question about the RESP_BIT. It seems it's only used for the 0x08 command.
If MCU want to read the result from chip 15, MCU will send out 0x080F. The spec says the RESP bit is set to 1, so that means the return format shall be 0x18FFDATA but it also says JOB_ID is Y i.e. 0xY8NNDATA. However the Job ID can be from 1 to 4. So there is a conflict, how does it represent Job ID#2 ? If it send out 0x28NNDATA then the RESP bit is not set, if the RESP bit is set, it would be 0x38NNDATA.
Does this mean that the JOB ID occupies the upper two bits?
i.e.
Return format:
32'b aabb1000NNNNNNNNDATADATADATADATA
where aa = job ID, bb = resp bit
Please clarify
If MCU want to read the result from chip 15, MCU will send out 0x080F. The spec says the RESP bit is set to 1, so that means the return format shall be 0x18FFDATA but it also says JOB_ID is Y i.e. 0xY8NNDATA. However the Job ID can be from 1 to 4. So there is a conflict, how does it represent Job ID#2 ? If it send out 0x28NNDATA then the RESP bit is not set, if the RESP bit is set, it would be 0x38NNDATA.
Does this mean that the JOB ID occupies the upper two bits?
i.e.
Return format:
32'b aabb1000NNNNNNNNDATADATADATADATA
where aa = job ID, bb = resp bit
Please clarify
Re: [OPEN] Bitmine CoinCraft 28nm chip distribution (December W50, 42.5BTC/THps)
Does the chip has internal oscillator?
There is IN_CLOCK pin. Does the chip requires an external generator?
There is IN_CLOCK pin. Does the chip requires an external generator?
I think the IN_CLOCK pin is for SPI only, there is a PLL inside the chip.
FUD everywhere by people who can't do math.
1. these are not batch #1,2 or 3 units.
2. all the openWRT firmware is burnt from a single image in batches,
3. the openWRT is used in more than just production units.
4. all burn-in is 24 or more hours, you all think we seriously only would have 700+ bitcoins if they were mining? LOL
I can't believe I'm repeating myself by saying we are not mining with batch #2 or #3 units.
5. complains will just lead into refunds, since clearly people are not happy with Avalon ASIC.
personally I'd love to issue these refunds so these people can go find the next thing to complain about and I can get some peace n quiet.
6. I'm going back to deal with trade-in and damaged orders.
1. these are not batch #1,2 or 3 units.
2. all the openWRT firmware is burnt from a single image in batches,
3. the openWRT is used in more than just production units.
4. all burn-in is 24 or more hours, you all think we seriously only would have 700+ bitcoins if they were mining? LOL
I can't believe I'm repeating myself by saying we are not mining with batch #2 or #3 units.
5. complains will just lead into refunds, since clearly people are not happy with Avalon ASIC.
personally I'd love to issue these refunds so these people can go find the next thing to complain about and I can get some peace n quiet.
6. I'm going back to deal with trade-in and damaged orders.
Hi BitSyncom
How would the refund work? I am actually looking to sell my batch 3 as my family in visiting my small apartment. I would rather get a refund immediately than deal with escrow and all those issues?
Thanks!
open a ticket and pick the trouble type as REFUND.
support.avalon-asic.com
Thanks a lot BitSyncom, I just submitted the ticket
Update:
A friend from the forum "yantis" asked me to cancel the ticket and bought the unit from me. I cancelled the ticket and we had a successful trade. He paid in full ^_^!!
FUD everywhere by people who can't do math.
1. these are not batch #1,2 or 3 units.
2. all the openWRT firmware is burnt from a single image in batches,
3. the openWRT is used in more than just production units.
4. all burn-in is 24 or more hours, you all think we seriously only would have 700+ bitcoins if they were mining? LOL
I can't believe I'm repeating myself by saying we are not mining with batch #2 or #3 units.
5. complains will just lead into refunds, since clearly people are not happy with Avalon ASIC.
personally I'd love to issue these refunds so these people can go find the next thing to complain about and I can get some peace n quiet.
6. I'm going back to deal with trade-in and damaged orders.
1. these are not batch #1,2 or 3 units.
2. all the openWRT firmware is burnt from a single image in batches,
3. the openWRT is used in more than just production units.
4. all burn-in is 24 or more hours, you all think we seriously only would have 700+ bitcoins if they were mining? LOL
I can't believe I'm repeating myself by saying we are not mining with batch #2 or #3 units.
5. complains will just lead into refunds, since clearly people are not happy with Avalon ASIC.
personally I'd love to issue these refunds so these people can go find the next thing to complain about and I can get some peace n quiet.
6. I'm going back to deal with trade-in and damaged orders.
Hi BitSyncom
How would the refund work? I am actually looking to sell my batch 3 as my family in visiting my small apartment. I would rather get a refund immediately than deal with escrow and all those issues?
Thanks!
Update:
A friend from the forum "yantis" asked me to cancel the refund ticket and bought the unit from me. I cancelled the ticket and we had a successful trade. He paid in full ^_^!!
this is a four module tho :/
unfortunately, batch 3 probably won't arrive until july. and by then, the margins are razor.
cloners coming out with 4 module avalons @ 36btc for 88g/hash.
and terrahash and kncminer taking preorders, risk is pretty high for asics.
let me know if price drops though, there is still opportunity if avalon gets there shit together.
but i paid more than 100 BTC for this..
Hi
I would like to sell my BFL preorder as I don't have the space to host it because my family is visiting me (I live in a small apartment).Shipping within US prefered!. It's a 60Gh/s unit order placed in early February.
Thanks!
I would like to sell my BFL preorder as I don't have the space to host it because my family is visiting me (I live in a small apartment).Shipping within US prefered!. It's a 60Gh/s unit order placed in early February.
Thanks!
Hi
I would like to sell my avalon batch 3 pre-order as I don't have the space to host it because my family is visiting me (I live in a small apartment). It's a #47xx preorder that's placed within minutes when the site opens. 4 module 85 Gh/s including PSU. Shipping within US prefered!.
Thanks!
I would like to sell my avalon batch 3 pre-order as I don't have the space to host it because my family is visiting me (I live in a small apartment). It's a #47xx preorder that's placed within minutes when the site opens. 4 module 85 Gh/s including PSU. Shipping within US prefered!.
Thanks!