Author

Topic: [ANN] Spondoolies-Tech - carrier grade, data center ready mining rigs - page 415. (Read 1260354 times)

hero member
Activity: 572
Merit: 500
It's already on the main page - search for string "miner-FL"

aka "hostname" ..  Grin Hard to say that just browsing GITHUB code. I realized it might be there already when Guy said that it starts with FL. When all GB units reach Canada, I'll know better.

Edit: I found this in the meantime, from one of your earlier posts.


sr. member
Activity: 462
Merit: 250
Let me get boring again, when will the GB start shipping?
The August Group Buy is scheduled to be shipped in the second part of August. That means some time after 25th of August so you will start using your miners in September.

You will also have to wait for compensation details until next week. The management couldn't have found few hours within last 4 weeks for the meeting to decide what kind of compensation they should offer.
hero member
Activity: 560
Merit: 500
Again, as I understand it, SP-T will  service all machines they built as per the warranty terms. For them if one is broken, it must be fixed, and it does not matter who owns it ..

I agree with Guy hare .. for the time being, just have the DC communicate it, and Zvi can update the MinePeon stats page to include it on the screen (below the MAC address) in the next software release. At least, when first powered up, you know what machine #ID you own. It still does not take out of the picture the "machine swap" before the first power-up in the end-user data-center, but at least you can track everything afterwards.



It's already on the main page - search for string "miner-FL"
hero member
Activity: 728
Merit: 500
Let me get boring again, when will the GB start shipping?
legendary
Activity: 3892
Merit: 4331
Currently, we don't email the serial ID before shipping.
It's very hard, if not impossible to implement.

At the risk of sounding 'paranoid', i don't see why it is difficult to sent such email (containing serial #) not before, but WITH order shipment notification.
A person who packs it could also record the serial # in the customers db, then customer service would email as part of shipment notification.
I get the point that DC can do it for you, but it is suboptimal, as it is not an independent confirmation with all due respect.
Having videochats with some customers would be really taxing in time, believe me, nobody would really want to do it if a simpler solution presents itself.
member
Activity: 104
Merit: 10
Currently, we don't email the serial ID before shipping.
It's very hard, if not impossible to implement.
We prepare the shipping documents in advance.
Flextronics select one tested machine randomly and attached the shipping documents.

Biodom, if it's important to you to know the serial, you can ask the DC owner to email it upon receiving the machine.

We'll try to find ways to improve the procedure, but it will take time.

Guy

This is really only an issue if you don't trust your hosting provider.

If a hosting provider received a defective SP30 that they personally own, it would be very easy for them to swap the defective unit with a good customer unit, and the customer would have no way to know this occurred.

It is a shocker if true, and goes somewhat against the claim that it is fully data center ready, in my opinion.
Bitcoin teaches us trust-less transactions. I don't want to find by trial and error who I should trust, although I always trust first, only to be discouraged sometimes afterwards.

In my opinion, it is easy to remedy. Just make sure that the initial host name (which contains eeprom number as Guy edited) can only be changed by the owner (using perl, for example) and send each owner email with perl login/unique passwd (no big deal using random passwd generator), otherwise it WILL stay FOREVER on default hostname that includes eeprom. If owner will try to change the hostname and it would not work, then it would mean that it is accidentally not his/her machine. In addition, DC owner would be asked to send info about what is customers equipment serial number BEFORE powering it up and connecting it to the net. I think that this is important from the point of ownership if you want to sell your machine. Obviously, you cannot sell what is not yours.

You are right, we have trust, but checking again on our side, is always better. If we are able to deduce the production week using the eeprom content is good to start with; Anyway having the serial number case/eeprom sent once the shipment begins is better.
hero member
Activity: 818
Merit: 1006
It is a shocker if true, and goes somewhat against the claim that it is fully data center ready, in my opinion.

In my opinion, it is easy to remedy. Just make sure that the initial host name (which contains eeprom number as Guy edited) can only be changed by the owner (using perl, for example) ...

All that needs to be changed is that the customer needs to be informed what their serial number is. You can always check the serial number, regardless of whether the hostname is currently the serial number or not.

I believe there is a sticker on the machine itself with that serial number/hostname in the back of the SP30 near the PSU. I'll check when I get to our datacenter later today.

If any of our customers are concerned about this issue, I am willing to video chat with them while unboxing their machines to give them a chance to record their serial number before we have a chance to swap it out. If you're less paranoid and trust us somewhat (which you probably do, if you're willing to send us miners in the first place), I can just write down and email you your FL serial numbers as I unbox them.
hero member
Activity: 818
Merit: 1006
Actually, it's trickier than that. You don't get 208V as an independent phase-to-neutral voltage. ... If instead you put one (7 amps) on AB, one on BC, and one on CA, then you get 14 amps on each phase. ...

This is incorrect, see this article:

http://www.raritan.com/blog/detail/how-to-calculate-current-on-a-3-phase-208v-rack-pdu-power-strip

Oh, thanks for the correction. I don't actually use this type of PDU, thus the mistake.
hero member
Activity: 572
Merit: 500
Definitely, if MBP wants SP-T miners to populate their data-centers in franchise I don't see why not.

Centralization and decentralization is a fun game . every 5-6 years there is a trend of one flavor or the other .. in an alternating manner.  And that can be seen across all industries. What we get out of it, eventually, is a central structure at the top with very mobile and empowered legs allowing the benefits and drawbacks of both. The extremes are being seen as the main changers over the short periods of time, until the environment adapts. There, one can profit or get hurt .. however, it pays to pick only the fruits of both sides.
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
Seems that spondoolies's side effect make appears some new business model !
For the good of the Bitcoin ecosystem: http://www.coindesk.com/gold-rush-arms-race-bitcoin-mining-north/

So, SPT wants to be MBP franchisee? I hope, not, but the article puts two together.

Quote
Corem continued by saying that the market seems to be moving in favor of centralization, but argued that other players in the space, including Spondoolies, are actively moving to keep the network as decentralized as possible. This can be seen in efforts like MegaBigPower’s franchisee program, which begun explicitly as a means of expanding the network’s capacity in a decentralized manner.
Nope.

We'll sell ASICs and miners to anyone interested to buy them though.
It was mentioned few pages ago that MBP has their own ASIC effort.

Guy
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
No method is really bullet-proof. The eeprom serial is saved in the management board.
In theory, the DC owner can replace ASICs boards and create better and worst machines.

I think that gmaxwell first suggested to burn the owner public key in the ASIC OTP.
(Last time I saw it here: https://en.bitcoin.it/wiki/Mining_manufacturer_tech_guidelines)

But I won't believe it will happen. Too complicated to implement.

Guy
legendary
Activity: 3892
Merit: 4331
Seems that spondoolies's side effect make appears some new business model !
For the good of the Bitcoin ecosystem: http://www.coindesk.com/gold-rush-arms-race-bitcoin-mining-north/

So, SPT wants to be MBP franchisee? I hope, not, but the article puts two together.

Quote
Corem continued by saying that the market seems to be moving in favor of centralization, but argued that other players in the space, including Spondoolies, are actively moving to keep the network as decentralized as possible. This can be seen in efforts like MegaBigPower’s franchisee program, which begun explicitly as a means of expanding the network’s capacity in a decentralized manner.
legendary
Activity: 3892
Merit: 4331
Currently, we don't email the serial ID before shipping.
It's very hard, if not impossible to implement.
We prepare the shipping documents in advance.
Flextronics select one tested machine randomly and attached the shipping documents.

Biodom, if it's important to you to know the serial, you can ask the DC owner to email it upon receiving the machine.

We'll try to find ways to improve the procedure, but it will take time.

Guy

This is really only an issue if you don't trust your hosting provider.

If a hosting provider received a defective SP30 that they personally own, it would be very easy for them to swap the defective unit with a good customer unit, and the customer would have no way to know this occurred.

It is a shocker if true, and goes somewhat against the claim that it is fully data center ready, in my opinion.
Bitcoin teaches us trust-less transactions. I don't want to find by trial and error who I should trust, although I always trust first, only to be discouraged sometimes afterwards.

In my opinion, it is easy to remedy. Just make sure that the initial host name (which contains eeprom number as Guy edited) can only be changed by the owner (using perl, for example) and send each owner email with perl login/unique passwd (no big deal using random passwd generator), otherwise it WILL stay FOREVER on default hostname that includes eeprom. If owner will try to change the hostname and it would not work, then it would mean that it is accidentally not his/her machine. In addition, DC owner would be asked to send info about what is customers equipment serial number BEFORE powering it up and connecting it to the net. I think that this is important from the point of ownership if you want to sell your machine. Obviously, you cannot sell what is not yours.
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
Seems that spondoolies's side effect make appears some new business model !
For the good of the Bitcoin ecosystem: http://www.coindesk.com/gold-rush-arms-race-bitcoin-mining-north/
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
Again, as I understand it, SP-T will  service all machines they built as per the warranty terms. For them if one is broken, it must be fixed, and it does not matter who owns it ..

I agree with Guy hare .. for the time being, just have the DC communicate it, and Zvi can update the MinePeon stats page to include it on the screen (below the MAC address) in the next software release. At least, when first powered up, you know what machine #ID you own. It still does not take out of the picture the "machine swap" before the first power-up in the end-user data-center, but at least you can track everything afterwards.
I admit that the method isn't bullet proof and needs to be improved. We'll look into it.
Of course we'll service any machine under warranty terms.
I've asked Zvisha to add the EEPROM serial #ID to UI

We're working on a list of DCs we'll recommend after proper due diligence by us.

Guy

Edit:
Note that the default hostname contains the EEPROM serial #. It begins with FL14:
http://storage.googleapis.com/spond_public/images/SP-30%20Hashrate.png
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
I guess big orders have priority over "meaningless" small orders
No. Wissam didn't wait and contacted us after receiving the newsletter with the spec change.
He was offered the same options everyone else will be offered.
Some others also contacts us and we usually find a common ground.
Next week we'll contact all the rest of the customers.
We're a very small team, please be patient and let us contact you.
We do hire more support staff.

Guy
hero member
Activity: 572
Merit: 500
Again, as I understand it, SP-T will  service all machines they built as per the warranty terms. For them if one is broken, it must be fixed, and it does not matter who owns it ..

I agree with Guy hare .. for the time being, just have the DC communicate it, and Zvi can update the MinePeon stats page to include it on the screen (below the MAC address) in the next software release. At least, when first powered up, you know what machine #ID you own. It still does not take out of the picture the "machine swap" before the first power-up in the end-user data-center, but at least you can track everything afterwards.

hero member
Activity: 742
Merit: 500
Currently, we don't email the serial ID before shipping.
It's very hard, if not impossible to implement.
We prepare the shipping documents in advance.
Flextronics select one tested machine randomly and attached the shipping documents.

Biodom, if it's important to you to know the serial, you can ask the DC owner to email it upon receiving the machine.

We'll try to find ways to improve the procedure, but it will take time.

Guy

This is really only an issue if you don't trust your hosting provider.

If a hosting provider received a defective SP30 that they personally own, it would be very easy for them to swap the defective unit with a good customer unit, and the customer would have no way to know this occurred.
donator
Activity: 1414
Merit: 1051
Spondoolies, Beam & DAGlabs
Currently, we don't email the serial ID before shipping.
It's very hard, if not impossible to implement.
We prepare the shipping documents in advance.
Flextronics select one tested machine randomly and attached the shipping documents.

Biodom, if it's important to you to know the serial, you can ask the DC owner to email it upon receiving the machine.

We'll try to find ways to improve the procedure, but it will take time.

Guy
hero member
Activity: 572
Merit: 500
No, what I'm saying is that one can get the ID from EEPROM_DEVICE=/sys/bus/i2c/devices/0-0050/eeprom, no matter what the machine is registered with.

When enabled, the machine reports back to SP-T hourly. That way, they can monitor what machines are used, what firmware they have, and notify the users for firmware updates. Keeping the script alive, SP-T will have a history on your machine very hard to fake. Once the code is changed, (as per my understanding) you lose the warranty. Why would a normal customer change it and lose all the benefits coming with SP-T support? How would I change my registration ID to match yours? Definitely if you keep your registration script working, SP-T will have your ID logged, together with all other registration data. They can definitely compare changes between the actual status and the recorded data while the unit was in the burn-test, first powered up .. and so on.

The EEPROM (Board) ID is not SW, nor FW. It's a hardware ID and does not depend on the firmware or the software installed on your machine.
Jump to: