[ANN][ENRG]Energycoin will be connected with StakeCoin for value creation!

[crypto4jan]

I loaded the energycoin-qt.exe from 2014 (1.1.2) which I saved from when I last used that machine because I got a message saying I still hold some.    The address given on the wallet startup is eCCHCWiK1PdQbiqRVRoT93ynQE3TMGXb8w

which doesnt match the one my name is registered with apparently.  I would guess the wallet specific data is not stored with the program I saved.  If Im trawling through files for that data file, whats the name I should be looking for

I guess it was in the registry but that windows is long gone.  Other files were libwinpthread-1.dll  and energycoin.conf which is 5 lines of text

This is the info from the original distribution list:

https://docs.google.com/spreadsheet/ccc?key=0AmtTPZS-lpnjdDQyOGQ2UmRNdGhWZ3g4T0xXREh5V3c&usp=drive_web#gid=0

Your username: STT   
Address: eK44ri3KkQh7dobQs72Mhf8QzFR3wdi82Y
https://chainz.cryptoid.info/enrg/address.dws?eK44ri3KkQh7dobQs72Mhf8QzFR3wdi82Y.htm
Total contains:    63,323.952191 ENRG

I think you lost the wallet.dat and just started the wallet.
The address you gave contains no ENRG: https://chainz.cryptoid.info/enrg/search.dws?q=eCCHCWiK1PdQbiqRVRoT93ynQE3TMGXb8w


Maybe you run on an other PC and did you made a backup from your wallet?

[1714065797]

1714065797

[1714065797]

1714065797

[1714065797]

1714065797

[1714065797]

1714065797

[1714065797]

1714065797

[1714065797]

1714065797

[crypto4jan]

The official EnergyCoin Core v.1.5.0 for both Windows and Linux
versions are now available at:
https://mega.nz/#F!uc0XmCra!73JBKfnmbdImd_9H_nXtRQ

Windows version:
SHA256 hash: 795CE14403A069D03C211F867BE23E34A7DF6CED66F2B60E6D30CE26EA101277
https://www.virustotal.com/en/file/795ce14403a069d03c211f867be23e34a7df6ced66f2b60e6d30ce26ea101277/analysis/

Linux version:
SHA256 hash: 0AF7BAF39233894219EBE5609691CEFF282247A5E705C89FC763D3CFE98852A5
https://www.virustotal.com/en/file/0af7baf39233894219ebe5609691ceff282247a5e705c89fc763d3cfe98852a5/analysis/

Latest source code has already been uploaded to:
https://github.com/EnergyCoinProject/energycoin

Algorithm: Scrypt POS
Fixed Block reward : 5 ENRG
Block Time: 90 seconds
Confirmations: 3 to confirm tx
Stake age: minimum 1 day to stake coins
Max stack age: 100 days

More details information about the fork schedule:
- v1.5 now has a new network protocol version 70003
- To give enough time for users to update the software, v1.5 will accept connecting to peers with both new and old protocol versions until March 23, 2016.
- After March 23, new software will stop accepting peers with old protocol version. This will ensure only new software will proceed to the new fork.
- After that, fork will actually occur at block height 2100000, and then the network will also stop accepting PoW blocks.

Some more changes that will be noticeable by normal users:
- new command on console:- sendsplit (allow users to split into multiple outputs easily when sending coins). For example, if users want to send 1000 x 1000 coins to address eXXXXXXXXXXXXXXXXXXXXXXXX.
The command should be:

sendsplit eXXXXXXXXXXXXXXXXXXXXXXXX '{"count":1000,"amount":1000}'

- getmininginfo command now contains staking-related information, including PoS weight and estimated time for reward.

[energycoin.operations]

RETWEET: https://twitter.com/GEO_Jan/status/702148667336216578

[fairglu]

Trying to compile latest github in Ubuntu 14 LTS, it fails with:

Code:

wallet.cpp: In member function 'bool CWallet::CreateCoinStake(const CKeyStore&, unsigned int, int64, CTransaction&)':
wallet.cpp:1524:87: error: no matching function for call to 'CWallet::SelectCoinsSimple(int64, unsigned int&, std::set<std::pair<const CWalletTx*, unsigned int> >&, int64&)'
     if (!SelectCoinsSimple(nBalance - nReserveBalance, txNew.nTime, setCoins, nValueIn))
                                                                                       ^
wallet.cpp:1524:87: note: candidate is:
wallet.cpp:1268:6: note: bool CWallet::SelectCoinsSimple(int64_t, unsigned int, std::set<std::pair<const CWalletTx*, unsigned int> >&, int64_t&) const
 bool CWallet::SelectCoinsSimple(int64_t nTargetValue, unsigned int nSpendTime, set<pair<const CWalletTx*,unsigned int> >& setCoinsRet, int64_t& nValueRet) const
      ^
wallet.cpp:1268:6: note:   no known conversion for argument 4 from 'int64 {aka long long int}' to 'int64_t& {aka long int&}'
make: *** [obj/wallet.o] Error 1

[Harcon]

This might clue you in. I just don't know if it's something you can fix.

http://stackoverflow.com/questions/11406304/no-conversion-from-long-unsigned-int-to-long-unsigned-int

[crypto4jan]

Trying to compile latest github in Ubuntu 14 LTS, it fails with:

Code:

wallet.cpp: In member function 'bool CWallet::CreateCoinStake(const CKeyStore&, unsigned int, int64, CTransaction&)':
wallet.cpp:1524:87: error: no matching function for call to 'CWallet::SelectCoinsSimple(int64, unsigned int&, std::set<std::pair<const CWalletTx*, unsigned int> >&, int64&)'
     if (!SelectCoinsSimple(nBalance - nReserveBalance, txNew.nTime, setCoins, nValueIn))
                                                                                       ^
wallet.cpp:1524:87: note: candidate is:
wallet.cpp:1268:6: note: bool CWallet::SelectCoinsSimple(int64_t, unsigned int, std::set<std::pair<const CWalletTx*, unsigned int> >&, int64_t&) const
 bool CWallet::SelectCoinsSimple(int64_t nTargetValue, unsigned int nSpendTime, set<pair<const CWalletTx*,unsigned int> >& setCoinsRet, int64_t& nValueRet) const
      ^
wallet.cpp:1268:6: note:   no known conversion for argument 4 from 'int64 {aka long long int}' to 'int64_t& {aka long int&}'
make: *** [obj/wallet.o] Error 1

The dev is informed and the compiled clients are okay.

[crypto4jan]

Let us know when you know how we can compile it ourselves  

It's never good to trust too much something already compiled.

That is ok and also the Rokos team is testing the source code.

[Harcon]

Let us know when you know how we can compile it ourselves  

It's never good to trust too much something already compiled.

 I can see why you would say that. That is why I tend to watch very carefully what I install. I can see both the calls it makes to the hardware and monitor what connections an app/ program makes. On the bright side, I have yet to install anything that was doing none advertised stuff on the system or online but maybe Im lucky.

 Development of my own in house OS starts the middle of the year, so, at that point I will be compiling everything. I am alarmed by the possibility that absolutely everything will become cloud based, so I am developing a closed system to be used only by me. 

[Harcon]

BTW, Is it my imagination, or is coindesk starting to run only Blockchain articles? At this rate might as well call it chaindesk.

 Any ETA on ROKOS Flavors? I realize they have their own site and thread but I am wondering if anyone has any info cuz Im to lazy to look. 

[lumeire]

BTW, Is it my imagination, or is coindesk starting to run only Blockchain articles? At this rate might as well call it chaindesk.

 Any ETA on ROKOS Flavors? I realize they have their own site and thread but I am wondering if anyone has any info cuz Im to lazy to look. 

It is only your imagination, seems you're a bit paranoid. 

@ontopic I'm having a trouble syncing, it's too slow and stuck at around May last year. Do you have a downloadable blk file available?

[Harcon]

BTW, Is it my imagination, or is coindesk starting to run only Blockchain articles? At this rate might as well call it chaindesk.

 Any ETA on ROKOS Flavors? I realize they have their own site and thread but I am wondering if anyone has any info cuz Im to lazy to look. 

It is only your imagination, seems you're a bit paranoid. 

@ontopic I'm having a trouble syncing, it's too slow and stuck at around May last year. Do you have a downloadable blk file available?

Energycoin bootstrap server:
https://copy.com/wVg3JYE147rDfy2M

[crypto4jan]

..
 Any ETA on ROKOS Flavors? I realize they have their own site and thread but I am wondering if anyone has any info cuz Im to lazy to look. 

I have email contact with Rikos team and they say next week:

2016-02-23 19:06 GMT+01:00 OK Cash <devteam@okcash.co>:

    Hi Jan,

    Perfect, I should do the testing on pi this week for ROKOS release for next week.

[energycoin.operations]

Let us know when you know how we can compile it ourselves  

It's never good to trust too much something already compiled.

That is ok and also the Rokos team is testing the source code.

The dev send some info for Fairglu and the blockexplorer is now running on 1.5!
There comes an addition to the source code on GitHub but source was okay.

[crypto4jan]

Nice to see we have now 8 Network Clients v1.5



Also good to see that the networks looks healty!

I have now a wallet running with 2000 blocks with size 1000-2500. On this page you can check what blocksize fits best for you.
Bigger blocks stake faster but smaller blocks are beter for the network.
The advised minimum is 1000 ENRG and that is also the default in the new client.
You can change that in the console to maximum 5000.

[crypto4jan]

Let us know when you know how we can compile it ourselves  

It's never good to trust too much something already compiled.

That is ok and also the Rokos team is testing the source code.

The dev send some info for Fairglu and the blockexplorer is now running on 1.5!
There comes an addition to the source code on GitHub but source was okay.

https://github.com/EnergyCoinProject/energycoin/commit/44dc5c9e0cc793348e68fa5b6f100e1e600a332f

Please note that there is actually no real difference in term of wallet functions with or without the patch. This is just a workaround.
People who could compile without the patch are not affected.

[STT]

Look for a wallet.dat on your whole disk

I should have known that lol  

Does this look hopeful ?  I swapped in a .dat but I have tons of them all unlabelled basically.   Now I think my wallet is really old, I can just swap in modern version update that and run it for a week ? and it'll look at the same directory for the wallet right

Maybe you run on an other PC and did you made a backup from your wallet?

Yea energy always ran on a laptop, I forget why it discontinued use but the laptop went through the wars and I would guess I had the sense to save the right files but not 100% sure

[kawa900jc]

In a few days rokos for ENRG can be download check: http://rokos.space/downloads.html

Official ROKOS v5 Flavors Wallpapers ready for every taste

Black



White

knip

[MyLucky7]

Nice to see we have now 8 Network Clients v1.5

I see the number is now 15 for v1.5.

I have also updated to v1.5, and it is running smooth.

Waiting for staking 5 ENRG after 2100000 soon.

[crypto4jan]

Nice to see we have now 8 Network Clients v1.5

I see the number is now 15 for v1.5.

I have also updated to v1.5, and it is running smooth.

Waiting for staking 5 ENRG after 2100000 soon.

Welcome MyLucky ENRG a good choice to invest and everybody has a chance to win each day 5 ENRG or more, depending how much blocks you have online.

[STT]

Gents! Is there a fresh(ish) ENRG blockchain available for download somewhere?

Check this:

Energycoin bootstrap server:
https://copy.com/wVg3JYE147rDfy2M

EnergyCoin.Conf

Code:

addnode=104.131.5.234
addnode= 73.7.107.243

addnode=54.213.236.81
addnode= 213.46.197.237

addnode=23.245.7.15
addnode=130.211.178.56


rpcport=22715
rpcallowip=127.0.0.1

rpcuser=user9
rpcpassword=pass9

Also add Energycoin.conf in EnergyCoin folder

I did that, the download is useful and I set the .conf file for nodes but it's still out of sync.     Would any of these switches be useful in helping me, Im not sure its making any progress doing anything

Code:

Options:
  -?                     This help message
  -conf=<file>           Specify configuration file (default: EnergyCoin.conf)
  -pid=<file>            Specify pid file (default: EnergyCoind.pid)
  -gen                   Generate coins
  -gen=0                 Don't generate coins
  -datadir=<dir>         Specify data directory
  -dbcache=<n>           Set database cache size in megabytes (default: 25)
  -dblogsize=<n>         Set database disk log size in megabytes (default: 100)
  -timeout=<n>           Specify connection timeout in milliseconds (default: 5000)
  -proxy=<ip:port>       Connect through socks proxy
  -socks=<n>             Select the version of socks proxy to use (4-5, default: 5)
  -tor=<ip:port>         Use proxy to reach tor hidden services (default: same as -proxy)
  -dns                   Allow DNS lookups for -addnode, -seednode and -connect
  -port=<port>           Listen for connections on <port> (default: 22705 or testnet: 22708)
  -maxconnections=<n>    Maintain at most <n> connections to peers (default: 125)
  -addnode=<ip>          Add a node to connect to and attempt to keep the connection open
  -connect=<ip>          Connect only to the specified node(s)
  -seednode=<ip>         Connect to a node to retrieve peer addresses, and disconnect
  -externalip=<ip>       Specify your own public address
  -onlynet=<net>         Only connect to nodes in network <net> (IPv4, IPv6 or Tor)
  -discover              Discover own IP address (default: 1 when listening and no -externalip)
  -listen                Accept connections from outside (default: 1 if no -proxy or -connect)
  -bind=<addr>           Bind to given address. Use [host]:port notation for IPv6
  -dnsseed               Find peers using DNS lookup (default: 0)
  -nosynccheckpoints     Disable sync checkpoints (default: 0)
  -banscore=<n>          Threshold for disconnecting misbehaving peers (default: 100)
  -bantime=<n>           Number of seconds to keep misbehaving peers from reconnecting (default: 86400)
  -maxreceivebuffer=<n>  Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)
  -maxsendbuffer=<n>     Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)
  -detachdb              Detach block and address databases. Increases shutdown time (default: 0)
  -paytxfee=<amt>        Fee per KB to add to transactions you send
  -server                Accept command line and JSON-RPC commands
  -testnet               Use the test network
  -debug                 Output extra debugging information. Implies all other -debug* options
  -debugnet              Output extra network debugging information
  -logtimestamps         Prepend debug output with timestamp
  -shrinkdebugfile       Shrink debug.log file on client startup (default: 1 when no -debug)
  -printtoconsole        Send trace/debug info to console instead of debug.log file
  -printtodebugger       Send trace/debug info to debugger
  -rpcuser=<user>        Username for JSON-RPC connections
  -rpcpassword=<pw>      Password for JSON-RPC connections
  -rpcport=<port>        Listen for JSON-RPC connections on <port> (default: 12147 or testnet: 30802)
  -rpcallowip=<ip>       Allow JSON-RPC connections from specified IP address
  -rpcconnect=<ip>       Send commands to node running on <ip> (default: 127.0.0.1)
  -blocknotify=<cmd>     Execute command when the best block changes (%s in cmd is replaced by block hash)
  -confchange            Require a confirmations for change (default: 0)
  -walletnotify=<cmd>    Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)
  -upgradewallet         Upgrade wallet to latest format
  -keypool=<n>           Set key pool size to <n> (default: 100)
  -rescan                Rescan the block chain for missing wallet transactions
  -salvagewallet         Attempt to recover private keys from a corrupt wallet.dat
  -checkblocks=<n>       How many blocks to check at startup (default: 250, 0 = all)
  -checklevel=<n>        How thorough the block verification is (0-6, default: 0)
  -loadblock=<file>      Imports blocks from external blk000?.dat file

Block creation options:
  -blockminsize=<n>      Set minimum block size in bytes (default: 0)
  -blockmaxsize=<n>      Set maximum block size in bytes (default: 250000)
  -blockprioritysize=<n> Set maximum size of high-priority/low-fee transactions in bytes (default: 27000)

SSL options: (see the Bitcoin Wiki for SSL setup instructions)
  -rpcssl                                  Use OpenSSL (https) for JSON-RPC connections
  -rpcsslcertificatechainfile=<file.cert>  Server certificate file (default: server.cert)
  -rpcsslprivatekeyfile=<file.pem>         Server private key (default: server.pem)
  -rpcsslciphers=<ciphers>                 Acceptable ciphers (default: TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH)

UI options:
  -lang=<lang>           Set language, for example "de_DE" (default: system locale)
  -min                   Start minimized
  -splash                Show splash screen on startup (default: 1)