Topic: [ANN] ** NEW SITE bitgem.pw ** BTG BitGem 0.4.9.ALPHA1 | COLORED COINS | FAUCET - page 33. (Read 147857 times)
July 21, 2013, 04:45:55 AM
How many BitGem developers are there? And what are they working on?
July 19, 2013, 04:30:44 PM
Anyone else notice that it's stuck on block 14064?
I pushed it through. At block 14093 now
July 18, 2013, 08:17:14 PM
Anyone else notice that it's stuck on block 14064?
July 17, 2013, 01:15:36 PM
fresh install (git clone)
/bin/bitgem/src> ./bitgemd getinfo
{
"version" : "v0.4.1-nvc-23-g92f265d-beta",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 13536,
"moneysupply" : 17717.25413800,
"connections" : 2,
"proxy" : "XXXXXXXXXXX",
"ip" : "XXXXXXX",
"difficulty" : 1.37620748,
"testnet" : false,
"keypoololdest" : 1374060342,
"keypoolsize" : 101,
"paytxfee" : 0.00100000,
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
}
/bin/bitgem/src>
The warning message is go out with last checkpoints.
You should to add secure nodes, delete database, rescan database.
I will rebuild gemWallet with last checkpoints.
Code:
{
"version" : "v0.4.1-nvc-23-g92f265d-beta",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 13899,
"moneysupply" : 17805.56815800,
"connections" : 8,
"proxy" : "",
"ip" : "",
"difficulty" : 1.85588469,
"testnet" : false,
"keypoololdest" : 1368696291,
"keypoolsize" : 101,
"paytxfee" : 0.00100000,
"errors" : ""
}
"version" : "v0.4.1-nvc-23-g92f265d-beta",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 13899,
"moneysupply" : 17805.56815800,
"connections" : 8,
"proxy" : "",
"ip" : "",
"difficulty" : 1.85588469,
"testnet" : false,
"keypoololdest" : 1368696291,
"keypoolsize" : 101,
"paytxfee" : 0.00100000,
"errors" : ""
}
Code:
[
{
"addr" : "188.126.8.14:7692",
"services" : "00000001",
"lastsend" : 1374089092,
"lastrecv" : 1374089092,
"conntime" : 1374087818,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13895,
"banscore" : 0
},
{
"addr" : "97.86.15.238:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374087825,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13895,
"banscore" : 0
},
{
"addr" : "178.32.218.153:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374088241,
"conntime" : 1374087826,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "50.89.148.247:7692",
"services" : "00000001",
"lastsend" : 1374088244,
"lastrecv" : 1374089092,
"conntime" : 1374087855,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13896,
"banscore" : 0
},
{
"addr" : "70.98.114.229:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374088654,
"conntime" : 1374087856,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "192.81.209.17:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374087875,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "199.192.205.46:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374088009,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13896,
"banscore" : 0
},
{
"addr" : "93.96.132.70:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374088210,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13898,
"banscore" : 0
}
]
{
"addr" : "188.126.8.14:7692",
"services" : "00000001",
"lastsend" : 1374089092,
"lastrecv" : 1374089092,
"conntime" : 1374087818,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13895,
"banscore" : 0
},
{
"addr" : "97.86.15.238:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374087825,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13895,
"banscore" : 0
},
{
"addr" : "178.32.218.153:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374088241,
"conntime" : 1374087826,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "50.89.148.247:7692",
"services" : "00000001",
"lastsend" : 1374088244,
"lastrecv" : 1374089092,
"conntime" : 1374087855,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13896,
"banscore" : 0
},
{
"addr" : "70.98.114.229:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374088654,
"conntime" : 1374087856,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "192.81.209.17:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374087875,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13536,
"banscore" : 0
},
{
"addr" : "199.192.205.46:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374088009,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13896,
"banscore" : 0
},
{
"addr" : "93.96.132.70:7692",
"services" : "00000001",
"lastsend" : 1374089093,
"lastrecv" : 1374089093,
"conntime" : 1374088210,
"version" : 60006,
"subver" : "/Satoshi:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13898,
"banscore" : 0
}
]
July 17, 2013, 06:57:53 AM
fresh install (git clone)
/bin/bitgem/src> ./bitgemd getinfo
{
"version" : "v0.4.1-nvc-23-g92f265d-beta",
"protocolversion" : 60006,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 13536,
"moneysupply" : 17717.25413800,
"connections" : 2,
"proxy" : "XXXXXXXXXXX",
"ip" : "XXXXXXX",
"difficulty" : 1.37620748,
"testnet" : false,
"keypoololdest" : 1374060342,
"keypoolsize" : 101,
"paytxfee" : 0.00100000,
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers."
}
/bin/bitgem/src>
July 16, 2013, 01:31:18 PM
Stake reward round fix has been succesfull.
Last stake rewards from previous month are being mined still, so it is provided current month RoI next.
Last stake rewards from previous month are being mined still, so it is provided current month RoI next.
good to know, keep up the good work mate
(show some love to the BTG community and keep us updated more frequently
) July 16, 2013, 01:26:28 PM
Stake reward round fix has been succesfull.
Last stake rewards from previous month are being mined still, so it is provided current month RoI next.
Last stake rewards from previous month are being mined still, so it is provided current month RoI next.
July 14, 2013, 01:53:47 AM
Thanks for responding!
At least I know what is going on now.
At least I know what is going on now.
July 14, 2013, 01:45:47 AM
Quite a few of the blocks I have mined recently - 1 in 5 is showing as Amount 0 in my wallet.
Take these transactions for example
http://btg.webboise.com:2750/chain/Bitgem
5ea59e2d3b3183e92292b81de71fdf1b1e32d1a5ec1cfdee7abdf3e83f0f3009
03cf49387a7b1951a808be79804b4b04de8590e824428b2d4a1939a50adf45e1
56a89210e81bf4cedaeb9c700fb194d232887791f4ced81de8bce734ff2ba5f1
f64659d821895ec5c75dfa52cc9a411839e8f711a7ca113b5f3f0af43282aa72
db294c2beb2d12b15aae462eee30c47b2046a9ee332ac0f36d31d50ca4bcf347
They are not showing as rejected by the network and are being confirmed but have zero amount.
Any ideas?
Take these transactions for example
http://btg.webboise.com:2750/chain/Bitgem
5ea59e2d3b3183e92292b81de71fdf1b1e32d1a5ec1cfdee7abdf3e83f0f3009
03cf49387a7b1951a808be79804b4b04de8590e824428b2d4a1939a50adf45e1
56a89210e81bf4cedaeb9c700fb194d232887791f4ced81de8bce734ff2ba5f1
f64659d821895ec5c75dfa52cc9a411839e8f711a7ca113b5f3f0af43282aa72
db294c2beb2d12b15aae462eee30c47b2046a9ee332ac0f36d31d50ca4bcf347
They are not showing as rejected by the network and are being confirmed but have zero amount.
Any ideas?
The blocks that are showing as 0 are PoS blocks. he current ROI for PoS is .0015% and rewards are being rounded to 0 the recent update applied a fix to this which will be active on July 15th
July 12, 2013, 05:20:22 AM
Quite a few of the blocks I have mined recently - 1 in 5 is showing as Amount 0 in my wallet.
Take these transactions for example
http://btg.webboise.com:2750/chain/Bitgem
5ea59e2d3b3183e92292b81de71fdf1b1e32d1a5ec1cfdee7abdf3e83f0f3009
03cf49387a7b1951a808be79804b4b04de8590e824428b2d4a1939a50adf45e1
56a89210e81bf4cedaeb9c700fb194d232887791f4ced81de8bce734ff2ba5f1
f64659d821895ec5c75dfa52cc9a411839e8f711a7ca113b5f3f0af43282aa72
db294c2beb2d12b15aae462eee30c47b2046a9ee332ac0f36d31d50ca4bcf347
They are not showing as rejected by the network and are being confirmed but have zero amount.
Any ideas?
Take these transactions for example
http://btg.webboise.com:2750/chain/Bitgem
5ea59e2d3b3183e92292b81de71fdf1b1e32d1a5ec1cfdee7abdf3e83f0f3009
03cf49387a7b1951a808be79804b4b04de8590e824428b2d4a1939a50adf45e1
56a89210e81bf4cedaeb9c700fb194d232887791f4ced81de8bce734ff2ba5f1
f64659d821895ec5c75dfa52cc9a411839e8f711a7ca113b5f3f0af43282aa72
db294c2beb2d12b15aae462eee30c47b2046a9ee332ac0f36d31d50ca4bcf347
They are not showing as rejected by the network and are being confirmed but have zero amount.
Any ideas?
July 10, 2013, 12:41:23 PM
uninstalled bitgem client, delete all except my wallet file. Still same warning.
Yep you will need to wait for the update. Dot worry about the warning for now. It will be fixed with the next release. Doesnt affect anything
July 10, 2013, 12:40:30 PM
Yes are there any other pools besides those two. The first has it maximum users reached and btg.binarycoins.eu, well I gave up about 2 days of work when it opened and had ~30 gem payout, then bam stats restarted and left me with 0.
I do and did understand the risks in a new pool, but damn did it hurt. There was also no announcement on their news tab about apologies or compensation, what a waste of hashing power. Hope i atleast helped the gentleman advance his coding techniques or something.
btg.binarycoins.eu is back up. My balance was still in my account. I would reccomend contacting the pool owner about that I do and did understand the risks in a new pool, but damn did it hurt. There was also no announcement on their news tab about apologies or compensation, what a waste of hashing power. Hope i atleast helped the gentleman advance his coding techniques or something.
July 10, 2013, 08:59:54 AM
Yes are there any other pools besides those two. The first has it maximum users reached and btg.binarycoins.eu, well I gave up about 2 days of work when it opened and had ~30 gem payout, then bam stats restarted and left me with 0.
I do and did understand the risks in a new pool, but damn did it hurt. There was also no announcement on their news tab about apologies or compensation, what a waste of hashing power. Hope i atleast helped the gentleman advance his coding techniques or something.
I do and did understand the risks in a new pool, but damn did it hurt. There was also no announcement on their news tab about apologies or compensation, what a waste of hashing power. Hope i atleast helped the gentleman advance his coding techniques or something.
July 10, 2013, 08:03:21 AM
uninstalled bitgem client, delete all except my wallet file. Still same warning.
July 10, 2013, 02:36:47 AM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
how do i update check point for the windows qt client?
You can either compile from sources or wait until the next QT release. Im not sure if its giving out the checkpoint warning still. Try redownloading the blockchain.
Close your client delete everything in appdata/roaming/bitgem except wallet.dat and bitgem.conf if you have one and restart the client
July 10, 2013, 02:28:03 AM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
how do i update check point for the windows qt client?
July 08, 2013, 03:18:19 PM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
I will depend on if they are considered as tagged or colored coins.
July 08, 2013, 01:53:44 PM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
I will depend on if they are considered as tagged or colored coins.
July 08, 2013, 11:37:01 AM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
July 08, 2013, 11:27:28 AM
Getting checkpoint is too old messages after updating the client and redownloading the blockchain.
Added checkpoints in https://github.com/bitgem/bitgem.
For gemwallet, I am finishing some developments, so you can rebuild the 'classic' client or wait a little with the WARINING message.
Remember it is needed to update to 0.4.1.5 version before 15 Jul and block #14,200. It is planned new rounded fix be from #14,200 block.
Some possible next directions of BTG include:
- tagged-coins,
- sticky transactions,
- true colored-coins.
I will write a more detailed post about it.
Jump to: