[ANN] Egano (EGN) Egalitarian & Anonymous single unit crypto based on CryptoNote

[CoinArt]

Sounds interesting....

[Atix]

I just resyncd the whole chain - no errors in daemon anymore.
BUT wallet still says, that there are no transfers (list_transfers), no balance (balance) and a reset doesn't change anything.
current bc_height 29076...
PLEASE HELP!

mining also does not work anymore...
I want the old version back.  

That's weird. Reset usually takes few minutes to rescan all blocks.
Close wallet, stop daemon. Open wallet, reset, close wallet. Run daemon again and once it is up open wallet and give it a few minutes to scan the chain.

I followed the instructions multiple times..

Both my wallets are still empty even after the 5 minute wallet sync.. What I did notice though is that sometimes after the reset it's synced immediately

displaying the right block height:
[wallet abcd1w]: bc_height
2018-Jan-19 20:20:48.138512 INFO    31341

EDIT: Checked out at commit cb69fc59124fa89f17516ff3b4c3d82804cc714e, built, resynced and the transactions are coming in.
         I forgot to clean up the ~/.egano directory, will clean up and try again with latest release

EDIT2: Nope, no balance with latest version..

[entropy0]

Seems like this pool (http://egano.cryptonight.me/) got every Single Block in the last time.
I would mine at this pool, but it seems like it's not paying.
Am I right?

correct, dev needs to help address issues with source i believe. can not pay when every block found is considered orphan

Good job dev, seem to have fixed the chain

However it seems to be issues with found blocks http://egano.cryptonight.me/#pool_blocks

From daemon:

Code:

 2018-Jan-18 20:47:52.032865 WARNING Transaction b1f9ed39f37cce35871414092572ad4c593f849621ed87ca11c0f5986568b42b is not valid. Reason: Transaction uses spent key image
2018-Jan-18 20:47:52.032927 INFO    [185.34.216.108:47767 OUT] Tx verification failed 

Chain seems fixed indeed and both version 1.1 and 1.2 of daemon now can sync, 28 blocks mined earlier around 29056-29084 became orphaned. Anyone who sent transactions yesterday should reset their wallet in the way MrCross did few posts above.
Don't worry of the invalid tx, it will be rejected until it completely disappears by expiring from the last mempool.
We are now above 31000. Thanks everyone for mining!

well i tried to, seems like simplewallet cant open the wallet file...

the issue with Tx fail is that pool sees it as invalid and therefore can not pay miners

What happens when you manually send payment from one of your wallets to another? Does it say Money successfully sent, Transaction too big, Internal node error or sth else?
My experience from one of my wallets is that when it generates a tx, it is accepted by the daemon but another node logs invalid transaction. The transaction gets to the mempool and is mined by the cryptonight pool. We will look into this further anyway, the blockchain cannot have double spends mined, at least not in the future.

there is something wrong with the source code, simplewallet does not open any wallet files for me

[egano]

Set up a node with 1.1 daemon, sync working to height 31475 (current max)
Running nodes with 1.2 daemon, sync working to the same height.
Blocks mined by pool seem to be accepted by other nodes. Transactions broadcasted at cca 31000 by our nodes were mined by the pool too. If your node sees this chain orphaned, please re-sync.
Testing old and new simplewallet against both versions of daemon and will post results here later.

[entropy0]

Set up a node with 1.1 daemon, sync working to height 31475 (current max)
Running nodes with 1.2 daemon, sync working to the same height.
Blocks mined by pool seem to be accepted by other nodes. Transactions broadcasted at cca 31000 by our nodes were mined by the pool too. If your node sees this chain orphaned, please re-sync.
Testing old and new simplewallet against both versions of daemon and will post results here later.

i've done re-sync again from block 1, let's see if that helps.

will probably still need to fix the TX error

[Stikyballs]

Payment still not working? no more tx error.

[entropy0]

Payment still not working? no more tx error.

blocks found by pool are not accepted but considered to be orphaned... might need some help figuring that out

also getting lots of this in daemon, not sure if related

Code:

2018-Jan-20 07:36:11.963565 WARNING [163.172.37.154:47767 OUT] Exception in connectionHandler: TcpConnection::read

also, simple wallet needs to be able to open wallets generated by walletd, otherwise we are not able to transfer balance out of it

[egano]

Payment still not working? no more tx error.

blocks found by pool are not accepted but considered to be orphaned... might need some help figuring that out

also getting lots of this in daemon, not sure if related

Code:

2018-Jan-20 07:36:11.963565 WARNING [163.172.37.154:47767 OUT] Exception in connectionHandler: TcpConnection::read

also, simple wallet needs to be able to open wallets generated by walletd, otherwise we are not able to transfer balance out of it

it seems that blocks mined by your pool are added to the blockchain in the end, see some blocks missing in your list, that means there is someone else's block on top of yours every few blocks. Working to resolve walletd vs simplewallet issue

[entropy0]

Payment still not working? no more tx error.

blocks found by pool are not accepted but considered to be orphaned... might need some help figuring that out

also getting lots of this in daemon, not sure if related

Code:

2018-Jan-20 07:36:11.963565 WARNING [163.172.37.154:47767 OUT] Exception in connectionHandler: TcpConnection::read

also, simple wallet needs to be able to open wallets generated by walletd, otherwise we are not able to transfer balance out of it

it seems that blocks mined by your pool are added to the blockchain in the end, see some blocks missing in your list, that means there is someone else's block on top of yours every few blocks. Working to resolve walletd vs simplewallet issue

cool thanks.

yes that confuses me too, as im not seeing an error - just that pool is considering all blocks to be orphaned...

[Atix]

I'm getting these too:

12:45:53.322952 INFO ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 29101
12:45:53.322952 INFO id:        <8a8d81a0bbe6ed7514f4aaccdedfa5461d4851fee1f901849d178e2f1473528b>
12:45:53.322952 INFO PoW:       <6ef45f6fdca33e0d11f2a90ec8fa4fc30bc2f55a7d8b31356937d4731efb0000>
12:45:53.322952 INFO difficulty:        23418
12:45:53.402943 INFO [163.172.37.154:47767 OUT] SYNCHRONIZED OK
12:45:53.815050 WARNING [163.172.37.154:47767 OUT] Exception in connectionHandler: TcpConnection::read

My pool seems to be in sync if I compare the mined block height with the other pool

Using pre update daemon & wallet

[egano]

I'm getting these too:

12:45:53.322952 INFO ----- BLOCK ADDED AS ALTERNATIVE ON HEIGHT 29101
12:45:53.322952 INFO id:        <8a8d81a0bbe6ed7514f4aaccdedfa5461d4851fee1f901849d178e2f1473528b>
12:45:53.322952 INFO PoW:       <6ef45f6fdca33e0d11f2a90ec8fa4fc30bc2f55a7d8b31356937d4731efb0000>
12:45:53.322952 INFO difficulty:        23418
12:45:53.402943 INFO [163.172.37.154:47767 OUT] SYNCHRONIZED OK
12:45:53.815050 WARNING [163.172.37.154:47767 OUT] Exception in connectionHandler: TcpConnection::read

My pool seems to be in sync if I compare the mined block height with the other pool

Using pre update daemon & wallet

This is somebody with daemon v1.1 who needs resync or run v1.2, then these blocks will be discarded.


Important: Bug was discovered in reset feature in simplewallet v1.2. For some reason it resyncs only since last alternate chain known by daemon (height 29059). If you don't see coins you received earlier, the easiest way is to stop daemon v1.2, start simplewallet v1.1, reset (reset was there already), close wallet, backup the wallet file (it is small and you can use it instead of reset later),   start daemon v1.1, wait for sync, start simplewallet 1.1, wait for the wallet to reload all txs (use reset again if it just shows prompt without reloading), check balance. Close wallet, backup wallet file again (to save its state), shut down v1.1 daemon and run v1.2 daemon and wallet.
Never run different version of simplewallet against different version of daemon, it will show nonsense balances and will not be able to sync after reset properly, throwing odd errors both in daemon and simplewallet. Even if you do so, follow the reset procedure above, your wallet keys and coins are always safe.

[egano]

also, simple wallet needs to be able to open wallets generated by walletd, otherwise we are not able to transfer balance out of it

walletd has a container file that can hold multiple wallets. These cannot be made compatible but walletd supports key export using the following RPC json function (same as for BCN):
https://wiki.bytecoin.org/wiki/Get_spend_keys_-_Bytecoin_RPC_Wallet_API

To workaround this simplewallet was added import/export keys feature. To export or import (or reset by re-create) a wallet you need both view key and spend key obtained from walletd API..

[entropy0]

also, simple wallet needs to be able to open wallets generated by walletd, otherwise we are not able to transfer balance out of it

walletd has a container file that can hold multiple wallets. These cannot be made compatible but walletd supports key export using the following RPC json function (same as for BCN):
https://wiki.bytecoin.org/wiki/Get_spend_keys_-_Bytecoin_RPC_Wallet_API

To workaround this simplewallet was added import/export keys feature. To export or import (or reset by re-create) a wallet you need both view key and spend key obtained from walletd API..

great thanks, now we just need to figure out why pools are not accepting blocks as found!

[egano]

great thanks, now we just need to figure out why pools are not accepting blocks as found!

Your pool egano.cryptonight.me finds blocks successfully, other nodes see it included in the blockchain. What errors do you get?

Code:

print_block 8dd81fc4814aefa7acb0c8013cc2e4094a912622990b4e99beeccfc984f2b96f
{"major_version":1,"miner_tx":{"extra":"01a60ce13b88e7d0d72ce6603a92eb7840db1cbe649d212f4f13ea140b1f49b72202080000000001724446","unlock_time":36445,"version":1,"vin":[{"type":"ff","value":{"height":36385}}],"vout":[{"amount":97,"target":{"data":{"key":"0d4b27ea48a5c996909fa4c27365959af705f291a25e50e06d652a28b6d1ac9e"},"type":"02"}},{"amount":900,"target":{"data":{"key":"a46f87ff0f320905101ec223c9b9c2675cac7b98205859b89dd71a48352090cb"},"type":"02"}},{"amount":9000,"target":{"data":{"key":"c8307e554a60e5d5f0051226c132c69ef8c152396ecf80fdadf6e1103a8d4d75"},"type":"02"}},{"amount":20000,"target":{"data":{"key":"fa57e854180060707b6683dab1feca4beb8f207bc7e14ad2e824495e6f9f9b9d"},"type":"02"}},{"amount":500000,"target":{"data":{"key":"37aa68fc50241d8e498e09682a7fe28ad328b3553d15ee865c832957470bbfc4"},"type":"02"}},{"amount":7000000,"target":{"data":{"key":"c943d1a4e41f263f32b871b245ebb1e653d006a36595416f25283678d7199055"},"type":"02"}},{"amount":50000000,"target":{"data":{"key":"88c7d1ce85b83c473b376b0e9acdb9bcda591a35ba83d195c46700c2fda77397"},"type":"02"}},{"amount":600000000,"target":{"data":{"key":"3e6447a30bdca2e020d8363fe1c32a680a36f257e1b96e2429dd4f45cd202ce9"},"type":"02"}},{"amount":8000000000,"target":{"data":{"key":"29edc5b7e0a56e9bdac96831090add20e1bae7bd755845570bf3553d4f7c40ad"},"type":"02"}},{"amount":60000000000,"target":{"data":{"key":"c10a051057fe6709fe26e5ea11fdcb63e82ac86cf9a60206ff8d9a0443a7de80"},"type":"02"}},{"amount":400000000000,"target":{"data":{"key":"e186353f2825ea522e0d4ba0cacce6a67cfddf4e07cac32cdf0972e9939090cd"},"type":"02"}}]},"minor_version":1,"nonce":"161a0000","prev_id":"13f14f7f2fca402b5ef11c1ac7d561fb7886acaa4537f3b67c7445ba09da05a0","timestamp":1516708614,"tx_hashes":[]}

[entropy0]

great thanks, now we just need to figure out why pools are not accepting blocks as found!

Your pool egano.cryptonight.me finds blocks successfully, other nodes see it included in the blockchain. What errors do you get?

Code:

print_block 8dd81fc4814aefa7acb0c8013cc2e4094a912622990b4e99beeccfc984f2b96f
{"major_version":1,"miner_tx":{"extra":"01a60ce13b88e7d0d72ce6603a92eb7840db1cbe649d212f4f13ea140b1f49b72202080000000001724446","unlock_time":36445,"version":1,"vin":[{"type":"ff","value":{"height":36385}}],"vout":[{"amount":97,"target":{"data":{"key":"0d4b27ea48a5c996909fa4c27365959af705f291a25e50e06d652a28b6d1ac9e"},"type":"02"}},{"amount":900,"target":{"data":{"key":"a46f87ff0f320905101ec223c9b9c2675cac7b98205859b89dd71a48352090cb"},"type":"02"}},{"amount":9000,"target":{"data":{"key":"c8307e554a60e5d5f0051226c132c69ef8c152396ecf80fdadf6e1103a8d4d75"},"type":"02"}},{"amount":20000,"target":{"data":{"key":"fa57e854180060707b6683dab1feca4beb8f207bc7e14ad2e824495e6f9f9b9d"},"type":"02"}},{"amount":500000,"target":{"data":{"key":"37aa68fc50241d8e498e09682a7fe28ad328b3553d15ee865c832957470bbfc4"},"type":"02"}},{"amount":7000000,"target":{"data":{"key":"c943d1a4e41f263f32b871b245ebb1e653d006a36595416f25283678d7199055"},"type":"02"}},{"amount":50000000,"target":{"data":{"key":"88c7d1ce85b83c473b376b0e9acdb9bcda591a35ba83d195c46700c2fda77397"},"type":"02"}},{"amount":600000000,"target":{"data":{"key":"3e6447a30bdca2e020d8363fe1c32a680a36f257e1b96e2429dd4f45cd202ce9"},"type":"02"}},{"amount":8000000000,"target":{"data":{"key":"29edc5b7e0a56e9bdac96831090add20e1bae7bd755845570bf3553d4f7c40ad"},"type":"02"}},{"amount":60000000000,"target":{"data":{"key":"c10a051057fe6709fe26e5ea11fdcb63e82ac86cf9a60206ff8d9a0443a7de80"},"type":"02"}},{"amount":400000000000,"target":{"data":{"key":"e186353f2825ea522e0d4ba0cacce6a67cfddf4e07cac32cdf0972e9939090cd"},"type":"02"}}]},"minor_version":1,"nonce":"161a0000","prev_id":"13f14f7f2fca402b5ef11c1ac7d561fb7886acaa4537f3b67c7445ba09da05a0","timestamp":1516708614,"tx_hashes":[]}

that's the thing, im not getting an error in pool - it just doesnt recognize the blocks and consider it orphaned - therefore no payments

[Atix]

Are you sure they are orphaned? Because your pool show the blocks as mined.
Check your pool wallet, should look like this when opening (while it loads the transactions)

Code:

Height 37624, transaction fd15f1d73df44b3a585e64fac6c3ce7454f0ee4997b916c9767c6f47b9a4e6e9, received 0.000000468380728257
Height 37625, transaction cea0a60868d4219932b3d944731aa23a16eca16ed9b4a077c7c795a5cfbdd3a4, received 0.000000468380504916
Height 37628, transaction 61e5bc59a4df9db0f0d8f6648bd5e870d8717a539fb8e8062ad532626ee86eb3, received 0.000000468379834893
Height 37630, transaction 9ee09a42e2936dc19c499c6c881fdb03956888a4ff96865f224783611bf113dc, received 0.000000468379388211
Height 37634, transaction 0f386c1c2ed3f704fd2b7c2fd14b17ab5931ac85837cb202632d344ae8d38c73, received 0.000000468378494849
Height 37636, transaction c031171ca48edd0147f3a698b87ca0dd17ec7467936884878e3eead01c7747e5, received 0.000000468378048168
Height 37642, transaction 4a7f40583ce16f98b6f223e6dfb6beb6653d16be4b78f44e7992c4581e992966, received 0.000000468376708130
Height 37642 of 37644

pool logs

Code:

2018-01-24 10:05:16 [unlocker] Unlocked 37586 block with reward 468389215307 and donation fee 0.02. Miners reward: 459021431001
2018-01-24 10:05:16 [unlocker] Block 37586 payment to abcd1w...................... for 37149 shares: 459021431001
2018-01-24 10:05:16 [unlocker] Unlocked 1 blocks and update balances for 1 workers

Code:

2018-01-24 10:06:53 [pool] (Thread 4) Block d93338 found at height 37648 by miner abcd1w...............@MYIP - submit result: {"status":"OK"}

Trying to send from pool wallet to miner wallet

Code:

2018-01-24 10:14:53 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Transaction size is too big"}
2018-01-24 10:14:53 [payments] Payments failed to send to {"amount":5000000000000,"address":"abcd1w..............."}
2018-01-24 10:14:53 [payments] Payments splintered and 0 successfully sent, 1 failed

[egano]

Trying to send from pool wallet to miner wallet

Code:

2018-01-24 10:14:53 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Transaction size is too big"}
2018-01-24 10:14:53 [payments] Payments failed to send to {"amount":5000000000000,"address":"abcd1w..............."}
2018-01-24 10:14:53 [payments] Payments splintered and 0 successfully sent, 1 failed

There are hardly any transactions in egano network, less than 2000 so far mostly from flooding tests, that's why block size and thus max transaction size is still small.
Sending 0.000005000000000000 often results in Transaction size too big error, but not always. It depends on inputs chosen and seems to be nondeterministic. Try sending slightly smaller amount (0.000004, 0.000003 and so on) two to five times with zero mixin and it will once go through. Remember that the change you get back from selected inputs is locked until the transaction is mined plus 60 blocks.

[Atix]

Trying to send from pool wallet to miner wallet

Code:

2018-01-24 10:14:53 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Transaction size is too big"}
2018-01-24 10:14:53 [payments] Payments failed to send to {"amount":5000000000000,"address":"abcd1w..............."}
2018-01-24 10:14:53 [payments] Payments splintered and 0 successfully sent, 1 failed

There are hardly any transactions in egano network, less than 2000 so far mostly from flooding tests, that's why block size and thus max transaction size is still small.
Sending 0.000005000000000000 often results in Transaction size too big error, but not always. It depends on inputs chosen and seems to be nondeterministic. Try sending slightly smaller amount (0.000004, 0.000003 and so on) two to five times with zero mixin and it will once go through. Remember that the change you get back from selected inputs is locked until the transaction is mined plus 60 blocks.

I just flooded the network with 1786 txs of 0.000001, got payments working on my pool. That amount is the maximum I can send in one tx.. I did manage to get a few 0.00005 working but only a few and then I got the tx size error.

I'm not familiar with CryptoNote, is it normal that the block rewards went down to around 0.000000124958082530 after my tx spam? I think the network needs to work out all the txs.. But why punish the miners by lowering the block reward?
Until now I set the mixins at 3 (pool default) but now it's telling me the number is too high due to the tx spam. I will set it at 0, no need for that functionality in a mining pool I guess.

[egano]

I just flooded the network with 1786 txs of 0.000001, got payments working on my pool. That amount is the maximum I can send in one tx.. I did manage to get a few 0.00005 working but only a few and then I got the tx size error.

I'm not familiar with CryptoNote, is it normal that the block rewards went down to around 0.000000124958082530 after my tx spam? I think the network needs to work out all the txs.. But why punish the miners by lowering the block reward?
Until now I set the mixins at 3 (pool default) but now it's telling me the number is too high due to the tx spam. I will set it at 0, no need for that functionality in a mining pool I guess.

The block reward is lower if a block is significantly bigger than previous average.
Your pool seems to be working all the time, but not on a list on 185.34.216.108, entropy0 took their one down.
The tx spam caused v1.1 daemon to report invalid blocks, the fix is to delete just blockscache.dat, no need to delete p2pcache or resync.

[Mig-23]

how to get this coins ? is there any exchange ?

i see no wallet for windows,when it will be come ?

how many total coins is it ?