there is nothing plugged into this usb port yet it is covered with yellow tape?
The yellow tape, kapton tape, is just to communicate to users that nothing should be plugged into this port (removing fuse F1 makes this port un-powered). Leave the tape. |
|
|
|
especially in china where bitcoin is illegal
Bitcoin is not illegal in China. At worst, it is in a grey area of the law. |
|
|
|
|
Thanks for this info peetah. Were you present at 1 of the 2 press events? Or are you reading about it online?
|
|
|
|
|
Sorry, no kit.
PS: I read your other thread; if you want bare chips, we can sell you some. Email me at m.bevand at gmail.com. We have a few dozens available today.
|
|
|
|
Cross-post: One of my Avalon units (batch #2) was delivered today Jun 27 by DHL, to the Los Angeles area. Ordered Feb 2, 2013. Paid 76.7 BTC (it was one of the orders affected by the walletbit bug: I was charged and paid 0.5 BTC, then sent the remaining ~76 BTC later in the day). After creating numerous (unanswered) tickets, my order was eventually added to the store in mid-June (order #108xx). I was emailed the tracking number yesterday. It travelled from Beijing to Los Angeles in 48h. Was not stopped at customs. Declared value = $500. Package weight was 16 kg (but declared as 0.5 kg on the shipping label). Avalon unit weight = 13.5 kg. It is a black chassis. Very few signs of use (slight traces of dust). Out of the box, cgminer was configured as is, confirming the know fact that Avalon mine with the units (I think for burn-in, which I don't mind): pool1
- url: stratum+tcp://stratum.ozco.in:80
- worker: avalon.default0
- password: 12345
pool2
- url: stratum+tcp://au.ozco.in:80
- worker: avalon.default0
- password: 12345
pool3
- url: stratum+tcp://mining.eligius.st:3334
- worker: 1AYdAw8CcrQ2wx55LTbFHRn5bxgNZhaRLW
- password: 12345
I am still waiting for my other batch #2 unit ordered on Feb 18. |
|
|
|
Congrats mrb! Odd that most seem to be getting tracking numbers prior to delivery, I received none.
They do it by adding the tracking number to the order, in the web store. Then the web store sends the update via email. Check your spam folder maybe. |
|
|
|
One of my Avalon units (batch #2) was delivered today Jun 27 by DHL, to the Los Angeles area. Ordered Feb 2, 2013. Paid 76.7 BTC (it was one of the orders affected by the walletbit bug: I was charged and paid 0.5 BTC, then sent the remaining ~76 BTC later in the day). After creating numerous (unanswered) tickets, my order was eventually added to the store in mid-June (order #108xx). I was emailed the tracking number yesterday. It travelled from Beijing to Los Angeles in 48h. Was not stopped at customs. Declared value = $500. Package weight was 16 kg (but declared as 0.5 kg on the shipping label). Avalon unit weight = 13.5 kg. It is a black chassis. Very few signs of use (slight traces of dust). Out of the box, cgminer was configured as is, confirming the know fact that Avalon mine with the units (I think for burn-in, which I don't mind): pool1
- url: stratum+tcp://stratum.ozco.in:80
- worker: avalon.default0
- password: 12345
pool2
- url: stratum+tcp://au.ozco.in:80
- worker: avalon.default0
- password: 12345
pool3
- url: stratum+tcp://mining.eligius.st:3334
- worker: 1AYdAw8CcrQ2wx55LTbFHRn5bxgNZhaRLW
- password: 12345
I am still waiting for my other batch #2 unit ordered on Feb 18. |
|
|
|
Got this too. So it looks like people who ordered the Chips early will be getting them soon. Curious to know which of the DIYers will be showcasing working miners first. Any guesses?
We will be first  ( working prototype) |
|
|
|
|
We are absolutely interested in doing assembly for those who have Avalon chips. But we work with minimum quantities of 10 thousand chips per customer. If you are interested, email me at m.bevand at gmail.com
|
|
|
|
|
Anybody owns a Single SC and can measure power consumption at the 12V level with a clamp meter (in other words not at the wall with a kill-a-watt or similar)?
|
|
|
|
that one in the middle is idle! fix that dude!  It was due to the April firmware somehow preloaded  well， I got one machine still using 419 firmware, so far so good, no orange lights for a longe time: Elapsed 2d 10h 57m 53s  MHSav 71658.45 FoundBlocks 0  Not suprising. At current diff, you need on average 14 days to solve a block with 1 Avalon. |
|
|
|
|
Thanks Micon, I confirm I received the 200 BTC from our bet.
This crypto escrow app works very well. Micon had actually misplaced his escrow code, but he merely had to ask the escrow (Dooglus) who had a copy of it. Escrow codes are effectively naturally redundantly distributed. Very cool.
|
|
|
|
- Payment types: we will be open to most options. - Yes we are in Orange County / LA. - I will not give any ETA. We prefer to surprise the community once products are ready to ship. good work mrb,
this is what we wanted to see in the beginning.
Well, I will transmit the thanks to my friends and partners who work on this project with me. |
|
|
|
|
To answer some questions:
- We are located in southern California.
- We will not take any money until the devices are all tested and ready-to-ship.
- We will likely sell via an auction. No price in mind for now.
- The chip and all the components have been soldered in a reflow oven.
- The picture shows bfgminer on the laptop (latest git version + some bugfixes from myself).
|
|
|
|
Wow. 1388 shares accepted in 6+ hours? That's a lot isn't it?
Well, no. That's equivalent to 275 Mh/s, because there is a single, lonely, puny ASIC in our prototype. A fully populated Avalon normally has 240 to 320 ASICs. |
|
|
|
PicoStocks is down for 1 day. A hacker obtained the password of a big shareholder of Proteon and started executing trades that led to a drop of the price of this asset. The hacker was able to transfer around 1300 BTC from PicoStocks to this account: https://blockchain.info/address/1PoYfqyTnxKdCpv5ydzEGepW5GLsRRHgBbWe will fix the damage today and the trading should continue tomorrow. We will reset the status of Proteon shares to previous state. Other shares were not affected. A PicoStocks account is supposed to be permanently tied to a specific Bitcoin address. How was the attacker able to withdraw to a seemingly arbitrary address? |
|
|
|
|
Show Posts
