Topic: [ANN] [GLB]Globe – One Currency for One Globe - Polished and Ready for Action - page 36. (Read 113608 times)
December 31, 2013, 09:36:37 AM
Cold storage wallets now in source code.
December 31, 2013, 08:59:53 AM
Sure. You can just commit the private key to the source code for now.
As I mentioned, if any member left the trusted committee, we need to create a new wallet, and transfer all funds from the old wallet to the new wallet, set a new password, encrypt it again, and update the git repository.
As I mentioned, if any member left the trusted committee, we need to create a new wallet, and transfer all funds from the old wallet to the new wallet, set a new password, encrypt it again, and update the git repository.
Yes this is true.
December 31, 2013, 12:13:39 AM
Any concern?
Don't hesitate to share your thoughts here.
Let's make it better
Don't hesitate to share your thoughts here.
Let's make it better
December 31, 2013, 12:10:57 AM
TAX is not always bad. The GLB creator (sphere) is not selfish. He tried and is trying his best to make the operation of reserved funds to everyone over the world.
Everyone can check from here:
http://www.globecrypto.com/#where-are-taxes-going-to
He has decided to put the reserved wallet to the public. This will be done in few days.
Good luck to all miners. :-)
Everyone can check from here:
http://www.globecrypto.com/#where-are-taxes-going-to
He has decided to put the reserved wallet to the public. This will be done in few days.
Good luck to all miners. :-)
December 31, 2013, 12:04:40 AM
ASIC miners, take a look at this ALT coin.
December 31, 2013, 12:01:53 AM
Good news!
The network hash rate is almost 1 TH/s. Actually, the estimated hash rate is: 821 GH/s.
You can simply get the network hash rate using following command:
python -c "diff=11471; print diff * 2**32 / 10**9 / 60;"
where the diff is current difficulty, which is 11471 now.
The network hash rate is almost 1 TH/s. Actually, the estimated hash rate is: 821 GH/s.
You can simply get the network hash rate using following command:
python -c "diff=11471; print diff * 2**32 / 10**9 / 60;"
where the diff is current difficulty, which is 11471 now.
December 30, 2013, 10:02:13 PM
Sure. You can just commit the private key to the source code for now.
As I mentioned, if any member left the trusted committee, we need to create a new wallet, and transfer all funds from the old wallet to the new wallet, set a new password, encrypt it again, and update the git repository.
As I mentioned, if any member left the trusted committee, we need to create a new wallet, and transfer all funds from the old wallet to the new wallet, set a new password, encrypt it again, and update the git repository.
December 30, 2013, 08:00:44 PM
Never mind found a way round it.
December 30, 2013, 06:50:26 PM
I think the best thing to do is use the same method of encrypting the private key with a password. Most practical method is to do what bcfanminer said. Put it all onto a nice spreadsheet on Google docs and also place the data in a nice .txt file in all the QTs and sourcecode. Does that sound like a good idea?
December 30, 2013, 06:40:01 PM
Agrrrr 
Sometimes when sending the binaries it tells me transaction is too small. I think we may need to find another way of distributing the reserves and price stabilization or embedding them into block-chain.
Sometimes when sending the binaries it tells me transaction is too small. I think we may need to find another way of distributing the reserves and price stabilization or embedding them into block-chain. December 30, 2013, 03:52:24 PM
Looks good.
By the way, if any member left the trusted committee, we need to create a new private key, and set a new password, and encrypt it again.
And put the new message into the block chain.
Otherwise, it is possible that the left guy could use the private key to deal with the reserved fund.
By the way, if any member left the trusted committee, we need to create a new private key, and set a new password, and encrypt it again.
And put the new message into the block chain.
Otherwise, it is possible that the left guy could use the private key to deal with the reserved fund.
December 30, 2013, 11:26:22 AM
Also thinking of using : https://code.google.com/p/immediatecrypt/
to encrypt private keys. It uses AES 256 encryption which is more secure than 128 bit AES encryption I was mentioning before
to encrypt private keys. It uses AES 256 encryption which is more secure than 128 bit AES encryption I was mentioning before
December 30, 2013, 10:49:36 AM
If everyone is Ok im going to start the embedding process.
December 30, 2013, 10:38:18 AM
Yep. Just testing the Wallet.dat deleting practice works fine. But note that the wallet must not contain any other funds as they will also be deleted.
December 30, 2013, 10:10:23 AM
Suggestion : do a GiveAway but only for people who are mining for some hours (they must post the Nick on the pool)
Yes I am going to do this once we have the reserves and price stabilization embedded into the block chain. I hope to start a giveaway tomorrow for miners
assuming I can start getting the reserves and price stabilization embedded into the block chain today. December 30, 2013, 09:51:26 AM
Suggestion : do a GiveAway but only for people who are mining for some hours (they must post the Nick on the pool)
+1
I suggest to prepare a plan for several giveaways in the next days so that people are encouraged to start mining GLB
December 30, 2013, 09:45:17 AM
Suggestion : do a GiveAway but only for people who are mining for some hours (they must post the Nick on the pool)
December 30, 2013, 09:35:42 AM
On another note is the P2P pool : http://www.japool.com:8680/static/ working ?
December 30, 2013, 07:58:28 AM
exchange yes, sorry.
December 30, 2013, 07:56:35 AM
Currently we absolutely need an exchanger !!!
Do you mean "exchange" ? If so agreed but others have mentioned that exchanges will only start accepting Globe if we have very high rate of hash this is why I am planning a giveaway that will increase the hash of the network.
Jump to: