|
Point taken. Thanks for the information.
|
|
|
|
|
Inappropriate post deleted.
|
|
|
|
See, math can be fun  |
|
|
|
|
What I think would be interesting is to verify:
y^2 mod p = ( x^3 + 7 ) mod p for G:
1) Calculate y^2 mod p, get answer
2) Calculate ( x^3 + 7 ) mod p, get answer
I believe that answer from 1) should equal answer from 2)
|
|
|
|
|
G is a public published value.
In compressed form it is:
G = 02 79BE667E F9DCBBAC 55A06295 CE870B07 029BFCDB 2DCE28D9 59F2815B 16F81798
and in uncompressed form it is:
G = 04 79BE667E F9DCBBAC 55A06295 CE870B07 029BFCDB 2DCE28D9 59F2815B 16F81798 483ADA77 26A3C465 5DA4FBFC 0E1108A8 FD17B448 A6855419 9C47D08F FB10D4B8
Each private key is secret but even if you have all but one of them you cannot calculate the last one you need to get to the final public key.
|
|
|
|
|
Just to answer your specific question about multiple key pairs. You can add together as many public keys as you want to and the corresponding private key will be the sum of all the private keys. I (and some others) are trying to come up with a way to use this property in a little side project we are working on. In our project, depending on how popular it gets, we may be adding together hundreds or even thousands of public keys and the private key would then be the sum of all the corresponding hundreds (or thousands) of private keys.
|
|
|
|
|
They were fine with me sending them deposits of dollars or BTC. I could sell BTC and buy BTC. But then they made me send them color photocopies of my driver's license and/or passport before I could remove any money or BTC from the account.
Maybe they were just picking on me and they do not do this to others? Anyone else?
|
|
|
|
|
Mike knows exactly how to do this - he did it in the example above to prove the concept.
So you two should get together!
|
|
|
|
I lol'ed. Why do you think I'd ever try this failed business idea? I have never tried selling bitcoins through paypal or google checkout. That would be business suicide. I am very sorry. This rumor may have started with my failure to read one of your posts as carefully as I should have. You said: one of our very own, AccessCoin.com had worked very hard on keeping fraud to a minimum by using Facebook to confirm identities, and even he has been shutdown by Google Checkout and accounts frozen. And upon my quick reading of this statement I incorrectly read that you were involved with AccessCoin.com and/or it was one of your businesses. I now see that you were using "our" as in the Bitcoin community. Sorry about that. I will get new reading glasses and be more careful in the future. |
|
|
|
Just got this back from dogisland (owner of StrongCoin): Thanks for contacting me.
Yes, I'll re-donate the fees. And add me in for 1 Per Charitable Organization ~ No Max
BTW I do see one (big?) difference between opening two or more accounts with the same private key and just sharing the password on a single account. In both cases all parties have total access to and any party can spend the coins. But in the case of sharing the password one person can change the password and not notify the others. In the case of multiple accounts with the same private key all parties can access and spend without regard to the password changes on other accounts. Edit: Actually there is no difference. The two parties we have selected will both have the private key so either one will always be able to figure out a way to get at the coins. For now I suggest we open one account at StrongCoin and move on to the next project: CO selection questions. I have an in at a small charity here in Denver: http://brentsplace.org (close friend had a child die of cancer and now his wife works there). BUT - I expect we want to target larger organizations? |
|
|
|
Just got this back from dogisland (owner of StrongCoin): Thanks for contacting me.
Yes, I'll re-donate the fees. And add me in for 1 Per Charitable Organization ~ No Max
|
|
|
|
|
Since it is for charity maybe he would waive the fee. I will ask him.
Two people importing the same private key into two separate accounts should work just fine.
Strongcoin was just a suggestion because I thought it would be easy. This can be done any number of ways.
|
|
|
|
Not sure what the dual private key bills have to do with this project. Perhaps you are suggesting we set up a dual private key system so that it takes two people to spend funds. I don't think that is needed in this case. We just need one trusted person to be able to spend the funds - just a normal single keypair account. Then we just need a backup person (or persons) that also have access to the same account. The main person and the backups all would just need the StrongCoin password in order to accomplish that. In addition to that it would not hurt to also back up the private key for safe keeping. |
|
|
|
I don't mind having a backup to the wallet/password to the account in the event of eventualities. I guess that won't involve a lot of work, unless something happens. I don't know if I'm known well enough in the community though. I suggest that once the vanity address is generated open an account at https://www.strongcoin.com and store it there and then give the passwords to both MemoryDealers (Roger) and Rassah so we have two people who can access the account. I would personally be ok with that. MemoryDealers hasn't publicly shown interest in being a hosting party for this project. I don't know if anyone approached him directly though. MemoryDealers did publicly express interest, see post #162 |
|
|
|
I suggest that once the vanity address is generated open an account at https://www.strongcoin.com and store it there and then give the passwords to both MemoryDealers (Roger) and Rassah so we have two people who can access the account. I would personally be ok with that. |
|
|
|
These are one time checks, not notes for circulation. They are designed for one time use just like the cheap paper checks in your check book. They are for those times when I want to give someone some BTC and I want to "write a check" and give it to them. The expectation is that they would then peel off the sticker and cash the check when they get a chance later on. Bills for circulation would need custom holograms (two holograms from two different trusted entities is my preference), higher quality paper, etc. There are a couple other thread discussing the creation of Bitcoin notes for circulation at https://bitcointalk.org/index.php?topic=52998.0 and https://bitcointalk.org/index.php?topic=53177.0If you read these threads you will find that the design is coming along nicely. |
|
|
|
The easiest way to redeem one of these accounts into an electronic wallet or online account is not Mt Gox (who requires all sorts of ID etc. to set up an account) just open a https://www.strongcoin.com account and then import the private key. Done. |
|
|
|
Sounds good. You are right about not being able to look up firstbits on a nonfunded account (what was I thinking?). That is why we have peer review, right?
1) Make the item with spots for two holograms and a final public key address
2) First party gets the item
3) Put the first private key in mini private key format under the first hologram
4) Ship the item along with the actual public key to the second party
5) Second party puts the second hologram on the item
6) Second private key in mini private key format under the second hologram
7) then adds the two public keys together, creating the final public key
9) From the final public key calculate the final public key address
10) This final public key adddress is etched/printed on the item somewhere, possibly on the hologram
11) The BTC funds are transmitted to the final public key address
At this point no one could possibly know the private key since it has never even been calculated.
To redeem:
1) Pull off both stickers
2) Get the two private keys
3) At a web site that supports the two key option, enter both private keys (Mt Gox, StrongCoin, etc. could be talked into supporting this option)
4) The web sites that support this option would then simply add the two private keys together
5) You now have the private key for the combined public key address etched/printed on the item
6) Redeem the BTC from the item
The other redemption options mentioned above are also possible.
|
|
|
|
Here is my explaination from another thread:
1) Make the bar or paper bill with spots for two holograms and a final public key address
2) First party gets the item
3) Put the first private key in mini private key format under the first hologram
4) Put the firstbits of the public key address on the outside of the first hologram
5) Ship the item along with the actual public key to the second party
6) Second party puts the second hologram on the item
7) Second private key in mini private key format under the second hologram
8. Firstbits of the second public key address on the outside of the hologram
9) NOW the second party verifies the public key shipped with the item with the public key address on the first hologram
10) then adds the two public keys together, creating the final public key
11) From the final public key calculate the final public key address
12) This final public key adddress is etched/printed on the item.
13) The BTC funds are transmitted to the final public key address The bolded steps are incorrect. There is no address for the two partial keys. There is also no reason to record the two partial public keys because they can't be looked up. You can't get a firstbits of a non-existent address. Remove/change steps 4, 8, 9 and it is a good summary. In the redeeming section for section 4 I would indicate you have multiple options a) use a website which supports dual private keys b) use a standalone client designed for loading dual private keys c) use a simple non-networked application which generates the single key from the dual private keys and use it anywhere a single private key can be used. As for what to put print on the hologram a) nothing b) some serial number which could be used to lookup the partial public key (not very useful) c) the combined public key (i.e. step 10). This would require some pre-coordination between two parties. A is the easiest. B isn't too tough but doesn't provide much value. C is the best but may requires some pre-coordination. |
|
|
|
|
Show Posts
