Pages:
Author

Topic: [ANN][GRE] GreenCoin - A Blockchain-Based Social Carbon Ecosystem - page 25. (Read 80466 times)

full member
Activity: 137
Merit: 100
yep, sorry about needing the conf and we'll ty to get the wallet to an installed version soon. The key here was getting a stable PoS coin out, which Ahmed did a terrific job getting accomplished, and from here we can start piling on the upgrades and features.

Gotcha, and thank you both for you efforts!
hero member
Activity: 579
Merit: 500
CoinQuacker
My node is listed twice above and I have currently 13 connections.
Are you sure you are running the very latest version of the wallet have reindexed/rescanned as per Ahmeds instructions?
I see two rejected/banned IPs in my logs, that's why I am asking.


Ok, found the problem: it has to be GreencoinV2.conf, not Greencoin.conf! Seriously, that is NOT obvious!

SO, I'm synced and staking! Tongue

yep, sorry about needing the conf and we'll ty to get the wallet to an installed version soon. The key here was getting a stable PoS coin out, which Ahmed did a terrific job getting accomplished, and from here we can start piling on the upgrades and features.
full member
Activity: 137
Merit: 100
My node is listed twice above and I have currently 13 connections.
Are you sure you are running the very latest version of the wallet have reindexed/rescanned as per Ahmeds instructions?
I see two rejected/banned IPs in my logs, that's why I am asking.


Ok, found the problem: it has to be GreencoinV2.conf, not Greencoin.conf! Seriously, that is NOT obvious!

SO, I'm synced and staking! Tongue
legendary
Activity: 1612
Merit: 1608
精神分析的爸
Ahmed said the seed node went off line but is back up. Here is my peer listing if you want to use addnode:



Thanks! Here is the conf version:

addnode=149.210.234.234:11517
addnode=212.243.7.37:11517
addnode=45.55.250.196:11517
addnode=94.211.9.70:11517
addnode=[2001:918:ffdf:320:dc88:47ff:fea6:dc8e]:11517
addnode=[2a01:7c8:aab9:45:5054:ff:fe19:4707]:11517
addnode=[2601:602:8b00:c5f5:4050:c88f:f16:7ca8]:55954


Thanks for this, makes it easier.

Not that it does any good, though, I have 0 connections...

My node is listed twice above and I have currently 13 connections.
Are you sure you are running the very latest version of the wallet have reindexed/rescanned as per Ahmeds instructions?
I see two rejected/banned IPs in my logs, that's why I am asking.

full member
Activity: 137
Merit: 100
Ahmed said the seed node went off line but is back up. Here is my peer listing if you want to use addnode:



Thanks! Here is the conf version:

addnode=149.210.234.234:11517
addnode=212.243.7.37:11517
addnode=45.55.250.196:11517
addnode=94.211.9.70:11517
addnode=[2001:918:ffdf:320:dc88:47ff:fea6:dc8e]:11517
addnode=[2a01:7c8:aab9:45:5054:ff:fe19:4707]:11517
addnode=[2601:602:8b00:c5f5:4050:c88f:f16:7ca8]:55954


Thanks for this, makes it easier.

Not that it does any good, though, I have 0 connections...
newbie
Activity: 42
Merit: 0
Ahmed said the seed node went off line but is back up. Here is my peer listing if you want to use addnode:



Thanks! Here is the conf version:

addnode=149.210.234.234:11517
addnode=212.243.7.37:11517
addnode=45.55.250.196:11517
addnode=94.211.9.70:11517
addnode=[2001:918:ffdf:320:dc88:47ff:fea6:dc8e]:11517
addnode=[2a01:7c8:aab9:45:5054:ff:fe19:4707]:11517
addnode=[2601:602:8b00:c5f5:4050:c88f:f16:7ca8]:55954


Thanks for this, makes it easier.
hero member
Activity: 579
Merit: 500
CoinQuacker
Producers: I am finalizing the set-up to payout the new coins. Here are some of the facts, comments, and forward-looking intentions as it relates to the first 11 days of this year and the completed PoS switchover, with respect to getting the Producer payout system back up and running fully:

The Foundation officially supported the old block chain until Block # 801739 (Block Time: January 2, 2016, 23:51:42 GMT)

The entire January 1st, 2016 payout day occurred before the end of this support (#800594 was the actual last block # a tx shows up).

January 2nd through January 7th I continued to pay out on the old chain. During this time the final status of a successful switch to PoS was uncertain. On January 9th (and before paying out the Jan 8 file), the PoS began working on the new chain, block #564 at time = 1/9/16 12:33 PM. Without a block explorer I went and found all of the blocks that occur just prior to 4 AM GMT, which is the official daily cutoff for payments going back to the first operating day. They are as follows:

Payout day   Block   Coins
1/9/16         2718   ~4,188,000
1/10/16       3567   ~1,698,000
1/11/16       4320   ~1,506,000

Today I successfully got the new Foundation wallet up and running on a linux machine. The coin amounts above are estimated. I know the balance of the Foundation wallet now and subtract back for the block # by 2000 coins/block. However, I don't know the exact balance at the given points in time so I will use these.

For the period of Jan 2-8 I was going to donate in coins to match the payouts that were made (calculated) on the old chain. Given that the first day of staking had a rather large total coin gross, I propose utilizing this 4.2M by spreading it over the 3 days prior, that is the 7th-9th, leaving me with the burden of only donating in for the 2nd through the 6th, which is still 5 days (~7M coins). That yields about 1.4M per day for those 3 days, which is close to the daily target of 720 block (1.44M coins).

 
hero member
Activity: 579
Merit: 500
CoinQuacker
that's cool idea.
using something like JSON format or other recognisable data format might be useful for more efficient parsing.

i recall some coins only like one OP_RETURN per block ?


edit.
although if you create your own consistent format you may be able to squeeze more data in Smiley (that of course does not preclude using a recognisable data format as well for your reduced info)
you could assume headers for example, so that information could be removed from input making it smaller

i.e. your example above, if you assume the headers/ordering you use
"P: 1; SYSTYPE: PVS; MR: 1200, MDIFF: 6.0; CC: 2.886; KGC: 2.8; TKGC 13842.3432"

becomes

"1; PVS; 1200; 6.0; 2.886; 2.8; 13842.3432"

I see. I was going for the key value pair but you don't think that's fruitful (i.e., not JSON-y?). There are two places to put data, the OP_RETURN could be encrypted but since this isn't personal info I didn't see the need for OP_RETURN use in this case, though the 1 OP_RETURN per block is troubling if anyone else knows about that.
legendary
Activity: 1638
Merit: 1036
that's cool idea.
using something like JSON format or other recognisable data format might be useful for more efficient parsing.

i recall some coins only like one OP_RETURN per block ?


edit.
although if you create your own consistent format you may be able to squeeze more data in Smiley (that of course does not preclude using a recognisable data format as well for your reduced info)
you could assume headers for example, so that information could be removed from input making it smaller

i.e. your example above, if you assume the headers/ordering you use
"P: 1; SYSTYPE: PVS; MR: 1200, MDIFF: 6.0; CC: 2.886; KGC: 2.8; TKGC 13842.3432"

becomes

"1; PVS; 1200; 6.0; 2.886; 2.8; 13842.3432"
hero member
Activity: 579
Merit: 500
CoinQuacker
I anticipate running 3 pays worth of Producer payouts tonight (1/9, 1/10, and 1/11). The totals won't match the website just yet because the website uses a formula to calculate coins based on the old blockchain. They will be paid base don the new daily coin totals which haven't been integrated at www.grcoin.com yet. I'll work backwards to get that to match as I update the web.

I also want to add data to the blockchain, something like "P: 1; SYSTYPE: PVS; MR: 1200, MDIFF: 6.0; CC: 2.886; KGC: 2.8; TKGC 13842.3432"

P = GreenCoin Foundation Renewable Producer #
SYSTYPE = System type (e.g. PVSolar or WV-Biodiesel)
MR = Meter read
MDIFF = meter differential from previous reading
CC: carbon conversion for given system type (i.e., PVsolar and Biofuel are different)
KG = carbon dioxide equivalent, in kg
TKG = total CO2 for that day among all producers

Comments can be added to payouts simply in quotes such as $./greencoind sendtoaddress [comment] [comment-to]
It can also be placed in the OP_RETURN

(not sure the difference between "comment" or "comment-to" if someone knows)

The reason for this is 3rd parties could build explorers and databases that makes use of this data for free. That might be helpful in expanding our carbon crediting imperative if people can see and utilize this information right off the blockchain.

So let me know any thoughts on that idea.
sr. member
Activity: 371
Merit: 250
Staking was working now after a reboot, nothing. Stake appears to be 0.

do I need to put in the line command "walletpassphrase

yes, anytime the client is closed and reopened.
Chris..thnx for the confirmation...now how do I ensure all my coins are staked?

I put the command line in and after 10 mins about 2% of available coins in my wallet are staking. How do I get it up to 100% staked? Yes, the coins are all >24 hours old...do I need the wallet on for 24 hours IOT to stake them?

I have never delved into PoS before so maybe a few lines on how PoS works, how to enable and the particulars of greencoin PoS might be useful in the near future.



I'm not quite sure if those #'s mean exactly what is staking or not. For a lot of other coins I have noticed it doesn't really reflect these splits. Maybe Ahmed can elaborate?

I also read up on the walletpassphrase command > rom https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list >>> walletpassphrase: Stores the wallet decryption key in memory for seconds.

Assuming a wallet is not encrypted, one should not need to re-enter the walletpassphrase for every reboot as the walletpass is not used. Is this correct?

Also, the staking amount on display goes between 0 to a few million, not all, yet the little electric zap symbol in the bottom left of the wallet states all coins staked...any idea which one is telling the truth? Note: the spendable coins are in line with the total - stake display.

A few notes on staking.  Your wallet needs to be unlocked to stake but if it was never encrypted it is by definition unlocked.  The value shown under “Stake” on the dashboard shows coins that are temporarily unavailable because they have recently staked (minted) a block.  These coins become available after 21 confirmations and begin to show up again in the “weight” shown under the little lighting bolt icon.  (There does not appear to be a 24 hour waiting period after the coins stake and I am very unclear what this is referring too.)

As more coins and wallets join up the time to stake a block will increase because you are competing with the other miners to earn the block reward and mint the next block.  At this point I'm showing a 12 hour wait to stake the next block.  If I go off-line with the wallet of course this time will go up because this is really just showing the chance of something happening based on the current conditions.  

I hope that helps a bit.
full member
Activity: 137
Merit: 100
Ahmed said the seed node went off line but is back up. Here is my peer listing if you want to use addnode:


Thanks! Here is the conf version:

addnode=149.210.234.234:11517
addnode=212.243.7.37:11517
addnode=45.55.250.196:11517
addnode=94.211.9.70:11517
addnode=[2001:918:ffdf:320:dc88:47ff:fea6:dc8e]:11517
addnode=[2a01:7c8:aab9:45:5054:ff:fe19:4707]:11517
addnode=[2601:602:8b00:c5f5:4050:c88f:f16:7ca8]:55954
hero member
Activity: 579
Merit: 500
CoinQuacker
Ahmed said the seed node went off line but is back up. Here is my peer listing if you want to use addnode:

Code:
[
{
"addr" : "149.210.234.234:11517",
"addrlocal" : "67.170.32.46:63417",
"services" : "00000001",
"lastsend" : 1452534208,
"lastrecv" : 1452534208,
"bytessent" : 10686,
"bytesrecv" : 8962,
"conntime" : 1452532045,
"timeoffset" : -6,
"pingtime" : 0.21500800,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3966,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "212.243.7.37:11517",
"addrlocal" : "67.170.32.46:63418",
"services" : "00000001",
"lastsend" : 1452534208,
"lastrecv" : 1452534208,
"bytessent" : 10779,
"bytesrecv" : 16735,
"conntime" : 1452532045,
"timeoffset" : -6,
"pingtime" : 0.21000800,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3966,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2a01:7c8:aab9:45:5054:ff:fe19:4707]:11517",
"addrlocal" : "[2601:602:8b00:c5f5:58fa:3695:b303:f5e7]:63419",
"services" : "00000001",
"lastsend" : 1452534208,
"lastrecv" : 1452534208,
"bytessent" : 5699,
"bytesrecv" : 4690,
"conntime" : 1452532046,
"timeoffset" : -6,
"pingtime" : 0.18000800,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3966,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "45.55.250.196:11517",
"addrlocal" : "67.170.32.46:63420",
"services" : "00000001",
"lastsend" : 1452534208,
"lastrecv" : 1452534208,
"bytessent" : 10418,
"bytesrecv" : 4347,
"conntime" : 1452532046,
"timeoffset" : -6,
"pingtime" : 0.14500400,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3966,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2001:918:ffdf:320:dc88:47ff:fea6:dc8e]:11517",
"addrlocal" : "[2601:602:8b00:c5f5:58fa:3695:b303:f5e7]:63431",
"services" : "00000001",
"lastsend" : 1452534198,
"lastrecv" : 1452534134,
"bytessent" : 4629,
"bytesrecv" : 5211,
"conntime" : 1452532092,
"timeoffset" : -5,
"pingtime" : 0.39000000,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3966,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "[2601:602:8b00:c5f5:4050:c88f:f16:7ca8]:55954",
"addrlocal" : "[2601:602:8b00:c5f5:58fa:3695:b303:f5e7]:11517",
"services" : "00000001",
"lastsend" : 1452534201,
"lastrecv" : 1452534201,
"bytessent" : 8757,
"bytesrecv" : 8295,
"conntime" : 1452532400,
"timeoffset" : 1,
"pingtime" : 0.00300000,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : true,
"startingheight" : 3970,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "94.211.9.70:11517",
"addrlocal" : "67.170.32.46:64007",
"services" : "00000001",
"lastsend" : 1452534198,
"lastrecv" : 1452534198,
"bytessent" : 3546,
"bytesrecv" : 1576,
"conntime" : 1452533549,
"timeoffset" : -5,
"pingtime" : 0.49600200,
"version" : 60018,
"subver" : "/Satoshi:1.2.1/",
"inbound" : false,
"startingheight" : 3980,
"banscore" : 0,
"syncnode" : false
}
]
full member
Activity: 137
Merit: 100
I've had 0 connections all day, is there something wrong?

Same-same, haven't synced for days... Nodes? Are the old ones still valid?
sr. member
Activity: 434
Merit: 250
I've had 0 connections all day, is there something wrong?
hero member
Activity: 810
Merit: 1000
Staking was working now after a reboot, nothing. Stake appears to be 0.

do I need to put in the line command "walletpassphrase

yes, anytime the client is closed and reopened.
Chris..thnx for the confirmation...now how do I ensure all my coins are staked?

I put the command line in and after 10 mins about 2% of available coins in my wallet are staking. How do I get it up to 100% staked? Yes, the coins are all >24 hours old...do I need the wallet on for 24 hours IOT to stake them?

I have never delved into PoS before so maybe a few lines on how PoS works, how to enable and the particulars of greencoin PoS might be useful in the near future.

I'm not quite sure if those #'s mean exactly what is staking or not. For a lot of other coins I have noticed it doesn't really reflect these splits. Maybe Ahmed can elaborate?

I also read up on the walletpassphrase command > rom https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list >>> walletpassphrase: Stores the wallet decryption key in memory for seconds.

Assuming a wallet is not encrypted, one should not need to re-enter the walletpassphrase for every reboot as the walletpass is not used. Is this correct?

Also, the staking amount on display goes between 0 to a few million, not all, yet the little electric zap symbol in the bottom left of the wallet states all coins staked...any idea which one is telling the truth? Note: the spendable coins are in line with the total - stake display.
hero member
Activity: 800
Merit: 1000
yep, the number of coins that will stake depend on what coins have weight, the difficulty, the coinage etc

Ahmed
hero member
Activity: 579
Merit: 500
CoinQuacker
Staking was working now after a reboot, nothing. Stake appears to be 0.

do I need to put in the line command "walletpassphrase

yes, anytime the client is closed and reopened.
Chris..thnx for the confirmation...now how do I ensure all my coins are staked?

I put the command line in and after 10 mins about 2% of available coins in my wallet are staking. How do I get it up to 100% staked? Yes, the coins are all >24 hours old...do I need the wallet on for 24 hours IOT to stake them?

I have never delved into PoS before so maybe a few lines on how PoS works, how to enable and the particulars of greencoin PoS might be useful in the near future.

I'm not quite sure if those #'s mean exactly what is staking or not. For a lot of other coins I have noticed it doesn't really reflect these splits. Maybe Ahmed can elaborate?
hero member
Activity: 810
Merit: 1000
Staking was working now after a reboot, nothing. Stake appears to be 0.

do I need to put in the line command "walletpassphrase

yes, anytime the client is closed and reopened.
Chris..thnx for the confirmation...now how do I ensure all my coins are staked?

I put the command line in and after 10 mins about 2% of available coins in my wallet are staking. How do I get it up to 100% staked? Yes, the coins are all >24 hours old...do I need the wallet on for 24 hours IOT to stake them?

I have never delved into PoS before so maybe a few lines on how PoS works, how to enable and the particulars of greencoin PoS might be useful in the near future.
hero member
Activity: 579
Merit: 500
CoinQuacker
Staking was working now after a reboot, nothing. Stake appears to be 0.

do I need to put in the line command "walletpassphrase

yes, anytime the client is closed and reopened.
Pages:
Jump to: