thundertoe
Legendary
Offline
Activity: 938
Merit: 1000
|
|
June 27, 2013, 02:29:54 AM |
|
These changes are so exciting! I'm up to 200 bitgems! Can't wait to see the variability merged in!
Nice!. Because 'carat effect', which does gems value exponential with carat, really your 200 BTGs are too valuable. You are lucky! Can you talk about this more? will there be changes to increase the pos rewards if you convert your gems vs not in the future updates?
|
|
|
|
MobGod
|
|
June 27, 2013, 02:48:30 AM |
|
anyone want to send me a gem or two?
|
|
|
|
MobGod
|
|
June 27, 2013, 07:56:24 AM |
|
Ok I've download the client but the gems don't show up running Linux why I compiled the qt but still nothing shows up for me
|
|
|
|
mineral (OP)
|
|
June 27, 2013, 08:05:09 AM |
|
Ok I've download the client but the gems don't show up running Linux why I compiled the qt but still nothing shows up for me
Ok, last commits related to Qt GemWallet are not into master branch. I will upload in a few days.
|
|
|
|
GoldBit89
|
|
June 27, 2013, 08:15:51 AM |
|
Getting
Warning:Checkpoint is too old.Wait for block chain to download, or notify developers.
what do now?
By the way , absolutely love the new look. it totally rocks.
Thanks.
|
FTC 6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4 BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61 |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
June 27, 2013, 08:19:05 AM |
|
Getting
Warning:Checkpoint is too old.Wait for block chain to download, or notify developers.
what do now?
By the way , absolutely love the new look. it totally rocks.
Thanks.
Are you running the gemwallet for windows? If so make sure it is the latest build. then delete everything in your appdata folder except your wallet.dat and .conf file. When you open the client the blockchain will download again and it should be goneI am also getting a checkpoint warning. I have not closed my wallet either. Just an FYI
|
|
|
|
GoldBit89
|
|
June 27, 2013, 08:25:59 AM |
|
Getting
Warning:Checkpoint is too old.Wait for block chain to download, or notify developers.
what do now?
By the way , absolutely love the new look. it totally rocks.
Thanks.
Are you running the gemwallet for windows? If so make sure it is the latest build. then delete everything in your appdata folder except your wallet.dat and .conf file. When you open the client the blockchain will download again and it should be gone i just downloaded the new 4.1.5 versons--both that are listed above. this error was in wallet before these 2 and after reinstalling still present in new installs.
|
FTC 6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4 BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61 |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
June 27, 2013, 08:36:50 AM |
|
Getting
Warning:Checkpoint is too old.Wait for block chain to download, or notify developers.
what do now?
By the way , absolutely love the new look. it totally rocks.
Thanks.
Are you running the gemwallet for windows? If so make sure it is the latest build. then delete everything in your appdata folder except your wallet.dat and .conf file. When you open the client the blockchain will download again and it should be gone i just downloaded the new 4.1.5 versons--both that are listed above. this error was in wallet before these 2 and after reinstalling still present in new installs. It has never been an issue in the past. It should be fixed with the next client
|
|
|
|
GoldBit89
|
|
June 27, 2013, 08:38:25 AM |
|
Getting
Warning:Checkpoint is too old.Wait for block chain to download, or notify developers.
what do now?
By the way , absolutely love the new look. it totally rocks.
Thanks.
Are you running the gemwallet for windows? If so make sure it is the latest build. then delete everything in your appdata folder except your wallet.dat and .conf file. When you open the client the blockchain will download again and it should be gone i just downloaded the new 4.1.5 versons--both that are listed above. this error was in wallet before these 2 and after reinstalling still present in new installs. It has never been an issue in the past. It should be fixed with the next client new client? 4.1.5 is new client right? REQUIRED UPDATE 0.4.1.5 BEFORE 15 JUL - Windows qt GemWallet installer: https://docs.google.com/file/d/0B9-QvC1XNoslUFdSVUlQb3BtRTA/edit?usp=sharingMD5SUM 86a80897d26af3027e3002b1cdb613f0 - Windows qt client installer: https://docs.google.com/file/d/0B9-QvC1XNoslTkhoVEkwWldzczA/edit?usp=sharingMD5SUM 4a16513906cf14d6c22c48e27e3a7106 - Source https://github.com/bitgem/bitgem
|
FTC 6nvzqqaCEizThvgMeC86MGzhAxGzKEtNH8 |WDC WckDxipCes2eBmxrUYEhrUfNNRZexKuYjR |BQC bSDm3XvauqWWnqrxfimw5wdHVDQDp2U8XU BOT EjcroqeMpZT4hphY4xYDzTQakwutpnufQR |BTG geLUGuJkhnvuft77ND6VrMvc8vxySKZBUz |LTC LhXbJMzCqLEzGBKgB2n73oce448BxX1dc4 BTC 1JPzHugtBtPwXgwMqt9rtdwRxxWyaZvk61 |ETH 0xA6cCD2Fb3AC2450646F8D8ebeb14f084F392ACFf
|
|
|
mullick
Legendary
Offline
Activity: 1064
Merit: 1002
|
|
June 27, 2013, 08:40:30 AM |
|
Yes I changed my post I have the warning as well
|
|
|
|
mineral (OP)
|
|
June 27, 2013, 08:52:29 AM |
|
Yes I changed my post I have the warning as well
These nodes addnode=178.32.218.153 addnode=70.98.114.229 addnode=98.18.252.73 addnode=50.137.233.14 addnode=50.2.8.67 addnode=85.228.201.126 addnode=92.240.244.44 deleting blockchain and deleting peers.dat are working for me.
|
|
|
|
|
MobGod
|
|
June 27, 2013, 02:22:45 PM |
|
meneral will that fix the warning issue ?
|
|
|
|
mineral (OP)
|
|
June 27, 2013, 02:38:50 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added.
|
|
|
|
MobGod
|
|
June 27, 2013, 03:16:02 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added. ok mineral not to be a pain in the ass can you post a example config file with the secure nodes i did what you said delete the peers.dat file recompiled the qt i downloaded and still got the warning so i want to try with a conf file to see if that will help
|
|
|
|
mineral (OP)
|
|
June 27, 2013, 03:34:26 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added. ok mineral not to be a pain in the ass can you post a example config file with the secure nodes i did what you said delete the peers.dat file recompiled the qt i downloaded and still got the warning so i want to try with a conf file to see if that will help You must to delete 'database' folder, 'blk0001.dat' and 'blkindex.dat' files in order to redownload blockchain, besides peers.dat . bitgem.conf # Use as many addnode= settings as you like to connect to specific peers addnode=178.32.218.153 addnode=70.98.114.229 addnode=98.18.252.73 addnode=50.137.233.14 addnode=50.2.8.67 addnode=85.228.201.126 addnode=92.240.244.44
# ... or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333
# Maximum number of inbound+outbound connections. maxconnections=200
# JSON-RPC options (for controlling a running ppcoind process)
#Server mode allows Qt to accept JSON-RPC commands server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=bitgemrpc rpcpassword=yourpassword
# How many seconds ppcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. #rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): rpcallowip=192.168.*.*
# Listen for RPC connections on this TCP port: rpcport=8348
# You can use ppcoind to send commands to ppcoind # running on another host using this option: rpcconnect=127.0.0.1
|
|
|
|
MobGod
|
|
June 27, 2013, 03:59:05 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added. ok mineral not to be a pain in the ass can you post a example config file with the secure nodes i did what you said delete the peers.dat file recompiled the qt i downloaded and still got the warning so i want to try with a conf file to see if that will help You must to delete 'database' folder, 'blk0001.dat' and 'blkindex.dat' files in order to redownload blockchain, besides peers.dat . bitgem.conf # Use as many addnode= settings as you like to connect to specific peers addnode=178.32.218.153 addnode=70.98.114.229 addnode=98.18.252.73 addnode=50.137.233.14 addnode=50.2.8.67 addnode=85.228.201.126 addnode=92.240.244.44
# ... or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333
# Maximum number of inbound+outbound connections. maxconnections=200
# JSON-RPC options (for controlling a running ppcoind process)
#Server mode allows Qt to accept JSON-RPC commands server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=bitgemrpc rpcpassword=yourpassword
# How many seconds ppcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. #rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): rpcallowip=192.168.*.*
# Listen for RPC connections on this TCP port: rpcport=8348
# You can use ppcoind to send commands to ppcoind # running on another host using this option: rpcconnect=127.0.0.1
ok i got the msg to go away thanks now for the last part i don't see the gems on the screen at all of the qt going to take a screen shot for you talking about the gemwallet http://tinypic.com/r/308b5n5/5
|
|
|
|
mineral (OP)
|
|
June 27, 2013, 04:21:07 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added. ok mineral not to be a pain in the ass can you post a example config file with the secure nodes i did what you said delete the peers.dat file recompiled the qt i downloaded and still got the warning so i want to try with a conf file to see if that will help You must to delete 'database' folder, 'blk0001.dat' and 'blkindex.dat' files in order to redownload blockchain, besides peers.dat . bitgem.conf # Use as many addnode= settings as you like to connect to specific peers addnode=178.32.218.153 addnode=70.98.114.229 addnode=98.18.252.73 addnode=50.137.233.14 addnode=50.2.8.67 addnode=85.228.201.126 addnode=92.240.244.44
# ... or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333
# Maximum number of inbound+outbound connections. maxconnections=200
# JSON-RPC options (for controlling a running ppcoind process)
#Server mode allows Qt to accept JSON-RPC commands server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=bitgemrpc rpcpassword=yourpassword
# How many seconds ppcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. #rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): rpcallowip=192.168.*.*
# Listen for RPC connections on this TCP port: rpcport=8348
# You can use ppcoind to send commands to ppcoind # running on another host using this option: rpcconnect=127.0.0.1
ok i got the msg to go away thanks now for the last part i don't see the gems on the screen at all of the qt going to take a screen shot for you talking about the gemwallet http://tinypic.com/r/308b5n5/5MobGod, I already told above commits of gemwallet are not merged into branch yet. TRy this build meanwhile : Added qt client linux 64 bits - Linux 64 bits GemWallet: https://docs.google.com/file/d/0B9-QvC1XNoslRnNRc2haWW51VUk/edit?usp=sharing MD5SUM: cdef3550da6d1a38c603e3ffe7bb4795
|
|
|
|
MobGod
|
|
June 27, 2013, 04:31:14 PM |
|
meneral will that fix the warning issue ? if you redownload the blockchain, deleting peers.dat and adding secure nodes not should to have the warning, beacuse last checkpoints have been added. ok mineral not to be a pain in the ass can you post a example config file with the secure nodes i did what you said delete the peers.dat file recompiled the qt i downloaded and still got the warning so i want to try with a conf file to see if that will help You must to delete 'database' folder, 'blk0001.dat' and 'blkindex.dat' files in order to redownload blockchain, besides peers.dat . bitgem.conf # Use as many addnode= settings as you like to connect to specific peers addnode=178.32.218.153 addnode=70.98.114.229 addnode=98.18.252.73 addnode=50.137.233.14 addnode=50.2.8.67 addnode=85.228.201.126 addnode=92.240.244.44
# ... or use as many connect= settings as you like to connect ONLY # to specific peers: #connect=69.164.218.197 #connect=10.0.0.1:8333
# Maximum number of inbound+outbound connections. maxconnections=200
# JSON-RPC options (for controlling a running ppcoind process)
#Server mode allows Qt to accept JSON-RPC commands server=1
# You must set rpcuser and rpcpassword to secure the JSON-RPC api rpcuser=bitgemrpc rpcpassword=yourpassword
# How many seconds ppcoin will wait for a complete RPC HTTP request. # after the HTTP connection is established. #rpctimeout=30
# By default, only RPC connections from localhost are allowed. Specify # as many rpcallowip= settings as you like to allow connections from # other hosts (and you may use * as a wildcard character): rpcallowip=192.168.*.*
# Listen for RPC connections on this TCP port: rpcport=8348
# You can use ppcoind to send commands to ppcoind # running on another host using this option: rpcconnect=127.0.0.1
ok i got the msg to go away thanks now for the last part i don't see the gems on the screen at all of the qt going to take a screen shot for you talking about the gemwallet http://tinypic.com/r/308b5n5/5MobGod, I already told above commits of gemwallet are not merged into branch yet. TRy this build meanwhile : Added qt client linux 64 bits - Linux 64 bits GemWallet: https://docs.google.com/file/d/0B9-QvC1XNoslRnNRc2haWW51VUk/edit?usp=sharing MD5SUM: cdef3550da6d1a38c603e3ffe7bb4795 mineral ok sorry didn't see that part so i just need to wait until you add it correct? I have that branch and it's running just no gems
|
|
|
|
Hazard
Legendary
Offline
Activity: 980
Merit: 1000
|
|
June 27, 2013, 04:39:11 PM |
|
This shit has to be a joke. GemWallet?
|
|
|
|
|