[BitFunder] IceDrill.ASIC IPO (235 Thash Mining Operation powered by HashFast)

[29750f0e1c2fbb3bb]

As stated previously, the majority of current ID funds are consolidated at 3N9MiKtPiAShS8tJMTpYocXTXRBSkQ2rpg.

Wasn't it more what you mined ages ago? *

the exact numbers are still in the processing, but the digest of the cash flow so far is that ID generated about 1750 BTC in its lifetime. 480 BTC are in the multi-sig address and about 120 BTC are floating around as additional reward reserve and not yet consolidated mining revenues. This is consistent with the fact that between February and May, ID accumulated about 650 BTC in surplus, and operated at break even thereafter. This means that ID upkeep consumed about 1150 BTC, the nature of it will be disclosed as soon as all transactions have been inspected.

[1714020796]

1714020796

[1714020796]

1714020796

[1714020796]

1714020796

[1714020796]

1714020796

[1714020796]

1714020796

[1714020796]

1714020796

[TheSwammi]

So what do I do when I've already registered a new payout address with CryptoMex (that has already received 2 payments) and I don't want to use the address associated with BitFunder? To me, the public facing BitFunder address was to be only that, public facing, and not to store funds. I do not want to transfer any funds to the BitFunder address because I consider it retired. Are you able to validate shares some other way? I can sign the BitFunder adddress, but that's about as far as I want to go.

I need to see a connection between the bitfunder account and the claim - and the best way for me is to that is to ask you to actually use the address. I can start making exceptions if need be, but please understand that there are >200 potentially active shareholder accounts and I want to keep the accounts as consistent as possible. Please PM me with your bitfunder address and a bitfunder signed message of the new account address you were using for cryptomex. I will then swap your BTC address on file after I verify the signature.

PM sent. Thanks for your time and quick response!

[monsieurmarc]

#ok transaction with the smallest amount created.

As one of the users with a tiny amount of shares I do wonder if making people with less than the magic number of 277 shares wait a year is sensible.  Look at the bitfunder list any a huge amount of people only have handfuls of shares and then a few have whopping amounts.

[Dice]

could someone explain what I actually do here:

"Create an OUTGOING transaction with two identical outputs with amounts of 0.13117745 using the BTC address in the final bitfunder shareholder database".

I once signed a message for an address and that's quite simple, could we just do that instead?

[pedrog]

We already signed a message with our Bitfunder address at icedrill.io, why this new requirement for an outgoing transaction?

[29750f0e1c2fbb3bb]

We already signed a message with our Bitfunder address at icedrill.io, why this new requirement for an outgoing transaction?

I have two lists, one from bitfunder and one from Willem. Doing an independent claim process allows me to check for consistency while at the same time not having to rely on either list. I understand that this is some additional effort but frankly it's as simple as creating a transaction. EVERYONE CAN CREATE A TRANSACTION - not everyone knows how to sign a message. Apart from that I chose this method because it allows algorithmic analysis of records in a trusted decentralized database.

could someone explain what I actually do here:

"Create an OUTGOING transaction with two identical outputs with amounts of 0.13117745 using the BTC address in the final bitfunder shareholder database".

I once signed a message for an address and that's quite simple, could we just do that instead?

see above.

#ok transaction with the smallest amount created.

As one of the users with a tiny amount of shares I do wonder if making people with less than the magic number of 277 shares wait a year is sensible.  Look at the bitfunder list any a huge amount of people only have handfuls of shares and then a few have whopping amounts.

We discussed buy backs as an option for small accounts, but the problem is impossible valuation of some of the assets. Paying out in advance for accounts below the minimum threshold would be an option we can discuss. It's a preferential treatment of small accounts though.

[29750f0e1c2fbb3bb]

I get people throwing signatures at me. While I can do some manual verification please be so kind and create the transaction I asked you to if you want to claim your address. You don't even have to contact me as the transaction and the bitfunder address listing is publicly visible.

I have created a sample transaction for everyone to inspect:
https://blockchain.info/tx/b6f8e59b0b21bcb58619c15f19bd7b29c09d0750eaaf43bb4da498ed70cf1447

It contains TWO 0.13117745 outputs. This is the clue for me. As stated before, if you want to submit a lesser amount of BTC I am also looking for a pair of either of the following amounts:
0.01311774,0.01311774
0.00131177,0.00131177
0.00013117,0.00013117

[29750f0e1c2fbb3bb]

I get people throwing signatures at me. While I can do some manual verification please be so kind and create the transaction I asked you to if you want to claim your address. You don't even have to contact me as the transaction and the bitfunder address listing is publicly visible.

I have created a sample transaction for everyone to inspect:
https://blockchain.info/tx/b6f8e59b0b21bcb58619c15f19bd7b29c09d0750eaaf43bb4da498ed70cf1447

It contains TWO 0.13117745 outputs. This is the clue for me. As stated before, if you want to submit a lesser amount of BTC I am also looking for a pair of either of the following amounts:
0.01311774,0.01311774
0.00131177,0.00131177
0.00013117,0.00013117

Under the rare circumstance that your wallet software doesn't allow to create transactions with multiple outputs, please make two separate transactions with the chosen amount and submit them to the blockchain within the same timeframe.

[molecular]

I get people throwing signatures at me. While I can do some manual verification please be so kind and create the transaction I asked you to if you want to claim your address. You don't even have to contact me as the transaction and the bitfunder address listing is publicly visible.

I have created a sample transaction for everyone to inspect:
https://blockchain.info/tx/b6f8e59b0b21bcb58619c15f19bd7b29c09d0750eaaf43bb4da498ed70cf1447

It contains TWO 0.13117745 outputs. This is the clue for me. As stated before, if you want to submit a lesser amount of BTC I am also looking for a pair of either of the following amounts:
0.01311774,0.01311774
0.00131177,0.00131177
0.00013117,0.00013117

can you tell us how to do this with bitcoind? Doesn't work out of box:

Code:

#> bitcoind sendmany "" "{\"1addy\":0.13117745,\"1addy\":0.13117745}"
error: {"code":-8,"message":"Invalid parameter, duplicated address: 1addy"}

you're making us jump through quite some hoops here. Why not just have us sign a message?

[fhh]

I get people throwing signatures at me. While I can do some manual verification please be so kind and create the transaction I asked you to if you want to claim your address. You don't even have to contact me as the transaction and the bitfunder address listing is publicly visible.

I have created a sample transaction for everyone to inspect:
https://blockchain.info/tx/b6f8e59b0b21bcb58619c15f19bd7b29c09d0750eaaf43bb4da498ed70cf1447

It contains TWO 0.13117745 outputs. This is the clue for me. As stated before, if you want to submit a lesser amount of BTC I am also looking for a pair of either of the following amounts:
0.01311774,0.01311774
0.00131177,0.00131177
0.00013117,0.00013117

this seems to be bullshit transaction spamming to the blockchain

I'll have to transfer funds to my bitfunder adress first because it is empty and then do this....


Who takes care of the missing payouts at cryptomex???
I'll also have this problem of a missing payout! something in the 0.03xxx range
its not vissible ... nowhere

I dont complain about not getting a positive roi out of this bullshit
but the handling of this fail is a disaster  

[29750f0e1c2fbb3bb]

this seems to be bullshit transaction spamming to the blockchain

I'll have to transfer funds to my bitfunder adress first because it is empty and then do this....
Who takes care of the missing payouts at cryptomex???
I'll also have this problem of a missing payout! something in the 0.03xxx range
its not vissible ... nowhere 

If there are missing payouts for cryptomex please send me the corresponding information via PM. All I can offer to make a note and resolve it within a reasonable time and/or let the cryptomex people sort it out.

On the notion of transaction spamming. It's not. Showing proof by an outgoing transaction on the address on which you will receive payments on makes very much sense. With the claim being on the ledger you actually have an automatic receipt of filing the claim. I see that you are one of many who are disgusted by being pushed around to get any payout back from this business. There is nothing I can change about previous procedures or experiences.

can you tell us how to do this with bitcoind? Doesn't work out of box:

Code:

#> bitcoind sendmany "" "{\"1addy\":0.13117745,\"1addy\":0.13117745}"
error: {"code":-8,"message":"Invalid parameter, duplicated address: 1addy"}

I realize now that the native client doesn't support the creation of the transaction I put up as an example. The problem seems that the JSON object kicks out the second argument b/c it is the same address. Wallet software like Armory will allow you to create the specified transaction.
Also: I asked for an OUTGOING transaction FROM the registered address with two outputs. You're free to choose different arbitrary target addresses and thus don't have the problem posed by bitcoind. But unless all inputs in your bitcoind wallets run on the bitfunder address you may pull the BTC from an arbitrary address and thus create and INCOMING transaction with two INPUTS of the specified amount. If you want to use a crude tool like bitcoind to create a qualifying transaction I recommend the following steps:

Code:

bitcoind setaccount "MYBITFUNDERADDRESS" "MYBITFUNDERACCOUNT"
bitcoind sendmany "MYBITFUNDERACCOUNT" "{\"RANDOMTARGETADDRESS1\":0.13117745,\"RANDOMTARGETADDRESS1\":0.13117745}"

And please make sure that MYBITFUNDERADDRESS has the necessary balance.  Sorry for the technical hurdle.

you're making us jump through quite some hoops here. Why not just have us sign a message?

Signing a message requires me to do manual verification and doesn't provide you with a confirmed receipt.

[lunarboy]

Most of us have confirmed our bitfunder address to gain access to the https://www.icedrill.io site, this to me is sufficient claim/proof of activity on that address no?

Crafting odd transactions is not possible with the software I use but i'll be happy to sign my address once again if it is absolutely necessary.  Surely you must appreciate the hoops everyone here has had to go through over the last 18 months. please make this simple.

[29750f0e1c2fbb3bb]

Most of us have confirmed our bitfunder address to gain access to the https://www.icedrill.io site, this to me is sufficient claim/proof of activity on that address no?

Crafting odd transactions is not possible with the software I use but i'll be happy to sign my address once again if it is absolutely necessary.  Surely you must appreciate the hoops everyone here has had to go through over the last 18 months. please make this simple.

In simple words the situation is complex. You may have confirmed your claim with willem, but not with me. You can reject this claim process and see what happens during the first payout on 12/1. You will have one year to ponder about what to do after which accounts without payouts are considered dead. Asking for making a transaction from the address you will receive payments on is appropriate. As noted earlier if your wallet software doesn't support multiple outputs, make two transactions within the same timeframe.

[Flashman]

Thank you for the positive step forward and the significantly more bitcoinlike method of dealing with the payouts.

Please understand however that a minority of users of this forum run a "full" wallet program any more, thus I would suspect only a a minority of shareholders are able to follow your instructions. Bear in mind it's not just a simple download at this time and may take days to synch up the 10s of gigabytes of blockchain before becoming functional.

I think it would be simpler therefore to outline a procedure that can be achieved easily with the blockchain.info wallet at least.

Also I am sure that had everyone known that the bitfunder address would end up tied to disparate entities when everything fell apart there, and that operations such as this would be required with it, then a different address and wallet  may have been used in the first place. I believe the only things required at the time were that you could sign messages from it as proof of control. Thus manually creating transactions may not have been a feature of the wallet originally tied to the address.

For myself, I am not tremendously confident messing with the command line, and worry that I can screw my wallet up with a typo. Particularly as the advice often given was asking how to create tx like that here, is "No , don't mess with it unless you know what you're doing" So n00b level info on that is hard to come by.

[29750f0e1c2fbb3bb]

Thank you for the positive step forward and the significantly more bitcoinlike method of dealing with the payouts.

Please understand however that a minority of users of this forum run a "full" wallet program any more, thus I would suspect only a a minority of shareholders are able to follow your instructions. Bear in mind it's not just a simple download at this time and may take days to synch up the 10s of gigabytes of blockchain before becoming functional.

I think it would be simpler therefore to outline a procedure that can be achieved easily with the blockchain.info wallet at least.

Also I am sure that had everyone known that the bitfunder address would end up tied to disparate entities when everything fell apart there, and that operations such as this would be required with it, then a different address and wallet  may have been used in the first place. I believe the only things required at the time were that you could sign messages from it as proof of control. Thus manually creating transactions may not have been a feature of the wallet originally tied to the address.

For myself, I am not tremendously confident messing with the command line, and worry that I can screw my wallet up with a typo. Particularly as the advice often given was asking how to create tx like that here, is "No , don't mess with it unless you know what you're doing" So n00b level info on that is hard to come by.

Thank you for the open and constructive feedback. Please note that the procedure is not arbitrarily chosen. It features several key characteristics I need: privacy, tamperproof receipt for filing claim, proof of technical skill level to withdraw funds.

Accounts which do not follow the claim procedure will likely have to be handed over to a lawyer and accountant. This is because I do not have proof that the account has shown the ability to withdraw funds, which means that these accounts will have to go through a legacy system to get repaid. Otherwise ID opens itself up to potential liability claims for sending funds to addresses with no counter-proof that the account had the ability to withdraw funds. I hope that clarifies a few question marks.

[iCEBREAKER]

Accounts which do not follow the claim procedure will likely have to be handed over to a lawyer and accountant. This is because I do not have proof that the account has shown the ability to withdraw funds, which means that these accounts will have to go through a legacy system to get repaid. Otherwise ID opens itself up to potential liability claims for sending funds to addresses with no counter-proof that the account had the ability to withdraw funds. I hope that clarifies a few question marks.

Do you really need to manually verify all the signed messages?  Who would bother to fake one, and for what purpose?

If I can sign a message I can also withdraw funds, as both require the same private key.

I really don't want to futz around with custom transactions because what little coin is in that wallet is fresh from the pool.

EDIT: iD still owns that chunk of Cointerra, right?

[wosinddiehirsche]

I use bitcoin core 0.93,

so please can me give someone a step to step instruction of what i have to do.

Thank you

[Hoofprint]

<---BTC balance 0,

between hasfast, mt gox, we.exchange, bitfunder and cryptomex.
you parasites have tapped me out.
how about we find away that dosent require me to give you more money

[Bargraphics]

<---BTC balance 0,

between hasfast, mt gox, we.exchange, bitfunder and cryptomex.
you parasites have tapped me out.
how about we find away that dosent require me to give you more money

You are sending a transaction to yourself (not to IceDrill) so you wouldn't be giving them more money.

If this simply isn't an option for you I'm sure you can PM 29750f0e1c2fbb3bb with what option works best for you and work something out.

[molecular]

can you tell us how to do this with bitcoind? Doesn't work out of box:

Code:

#> bitcoind sendmany "" "{\"1addy\":0.13117745,\"1addy\":0.13117745}"
error: {"code":-8,"message":"Invalid parameter, duplicated address: 1addy"}

I realize now that the native client doesn't support the creation of the transaction I put up as an example. The problem seems that the JSON object kicks out the second argument b/c it is the same address. Wallet software like Armory will allow you to create the specified transaction.
Also: I asked for an OUTGOING transaction FROM the registered address with two outputs. You're free to choose different arbitrary target

"Create an OUTGOING transaction with two identical outputs with amounts of 0.13117745 using the BTC address in the final bitfunder shareholder database".

From this I figured the outputs of the transaction would have to be using the BTC address. I guess it can be read that way, no?

Now what do I do. Move more fund to that address (for fee) and the make a transaction that has my BTC address as inputs?

addresses and thus don't have the problem posed by bitcoind. But unless all inputs in your bitcoind wallets run on the bitfunder address you may pull the BTC from an arbitrary address and thus create and INCOMING transaction with two INPUTS of the specified amount. If you want to use a crude tool like bitcoind to create a qualifying transaction I recommend the following steps:

Code:

bitcoind setaccount "MYBITFUNDERADDRESS" "MYBITFUNDERACCOUNT"
bitcoind sendmany "MYBITFUNDERACCOUNT" "{\"RANDOMTARGETADDRESS1\":0.13117745,\"RANDOMTARGETADDRESS1\":0.13117745}"

And please make sure that MYBITFUNDERADDRESS has the necessary balance.  Sorry for the technical hurdle.

you're making us jump through quite some hoops here. Why not just have us sign a message?

Signing a message requires me to do manual verification and doesn't provide you with a confirmed receipt.

my bitfunder address is in a electrum hd wallet. I'm certainly not going to export a private key from a HD wallet, so I have to construct the transaction using electrum (or hand-craft it and sign it with electrum or whatever)...

I'll see what I can do, but I'd like to note that this process is probably costing me more money (in the form of my time) than I will ever receive from icedrill.