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

[MrCross]

the pool is offline

[1714690189]

1714690189

[1714690189]

1714690189

[1714690189]

1714690189

[1714690189]

1714690189

[cleder]

I do not understand. Why do they start coins that have absolutely nothing ready? That is, the developer has a premine, he needs to do everything for him?

Same questions. This is only next "copy paste release" coin with absolutely no future.
Waste of time, waste of power.

[Bitoken]

Max supply: 1.0

Are you serious ? Can you explain us why do you setup this coin like that ?

[papilyn]

Max supply: 1.0

Are you serious ? Can you explain us why do you setup this coin like that ?

He just want to be cool.

[egano]

@egano
node up 163.172.37.154
would like reward to
abcd1wxyz4zjjP7fkdhpEX7EBrdcqZaCFP92BGuMPhNTCXYgW1nTAWZT4bP3zBue3HEiqSDeGtUJp3f dEyCR8KB6h9D4R2Sdw1J15nZ2
if possible, and if you find the node good enough (ssh disk dual core dedicated server 100mbps)

thanks for an interesting and different blockchain

Sent.
The bounty is usually sent at the end of week but to encourage growth the first week may be honored earlier.
Thanks!

[egano]

the pool is offline

yes, the pool was online for about an hour.
Of course we cannot rely on a single pool. Every new pool will be paid a bounty, smaller portion after setting up and the rest after reasonable uptime.

[egano]

Max supply: 1.0

Are you serious ? Can you explain us why do you setup this coin like that ?

It is better to know how big portion of total you have rather to set up a random big number as total supply. The representation then can be adjusted as needed: mEGN, µEGN, nEGN and so on.

[egano]

I do not understand. Why do they start coins that have absolutely nothing ready? That is, the developer has a premine, he needs to do everything for him?

Same questions. This is only next "copy paste release" coin with absolutely no future.
Waste of time, waste of power.

The cryptocurrency is up and running, that's why it was anncounced. The development although still in early stage is going on. Everyone who like the idea may benefit from early knowledge about egano and support it by mining, claiming bounties, developing tools or otherwise contributing. Unlike ICOs this is intended as fully community-contributed cryptocurrency with no exact ETAs of goals.

[Atix]

pubkey: abcd1wxyz3FH7vq6GfbgKwde7d6zG4dHyTNyb9wugqd2HR3uk3zh1eqHP2QDcxzdop3gWyEUBbvzDgA 6efiAb1NC1rBMB93nwWu1gdY8

Pool coming soon

addnode=185.34.216.108

[egano]

pubkey: abcd1wxyz3FH7vq6GfbgKwde7d6zG4dHyTNyb9wugqd2HR3uk3zh1eqHP2QDcxzdop3gWyEUBbvzDgA 6efiAb1NC1rBMB93nwWu1gdY8

Pool coming soon

addnode=185.34.216.108

Money successfully sent, transaction 414f2e96a85706a211bd7cf02f5d2cb572e9f33251d781d463028a724a934adb
Pool will be honored 4 µEGN after first day and 2 µEGN after each week of reasonable uptime, up to 10 µEGN total.

[novakmi]

I do not understand. Why do they start coins that have absolutely nothing ready? That is, the developer has a premine, he needs to do everything for him?

Same questions. This is only next "copy paste release" coin with absolutely no future.
Waste of time, waste of power.

Nothing ready? There is functional daemon and wallet, the other stuff is just optional.

Linux is free and available to anyone (if you have Windows, you can easily install Virtual Machine), what else would you need to start?

I must say, the developers even provided working Linux binaries for latest Ubuntu, which is very rare to see.  There is no need to recompile!
Just download and use. Many other cryptonote  "shining" coins  like Monero, Intense, Aeon, Sumo ... struggle with this and recompilation and fixing is needed.
This is positive sign for me.

[thegrey]

Everything seems to work just fine.
The 1 coin max supply is a bit quirky, but also makes the whole blockchain stand out.
Just for fun today may be interesting project tomorrow.
After the micro nano pico stuff is added I think it would be a bit more readable.
It is not so far from what is done with Iota and Miota.

[MrCross]

seems like the blockchain's "broken".
...doesn't get new blocks since a while now (hangin on block #19456).
Also getting an error in daemon like:

22:06:11.742850 INFO Wrong index in transaction inputs: 2007, expected maximum 2006
22:06:11.743141 INFO Failed to get output keys for tx with amount = 0.000000000000004000 and count indexes 1
22:06:11.743513 INFO Failed to check ring signature for tx <1fbedc7a8d6e044ff3b5562a03289e7f95c869af66316e56de5a75183243d1a2>
22:06:11.750720 INFO Wrong index in transaction inputs: 1965, expected maximum 1963
22:06:11.750976 INFO Failed to get output keys for tx with amount = 0.000000000000030000 and count indexes 1
22:06:11.751343 INFO Failed to check ring signature for tx <8833aa4a5650143a457ee4b1c1cc2a547274713a08a5be46c7adb7853f1f148e>
22:06:11.756499 INFO Wrong index in transaction inputs: 1973, expected maximum 1970
22:06:11.756678 INFO Failed to get output keys for tx with amount = 0.000000000070000000 and count indexes 1
22:06:11.756997 INFO Failed to check ring signature for tx <084581968d9c72c66509ebc2869b1c77d758eb02057cd0148d65c3aad884c20f>
22:06:11.793562 INFO Wrong index in transaction inputs: 93, expected maximum 92
22:06:11.793828 INFO Failed to get output keys for tx with amount = 0.000000060000000000 and count indexes 1
22:06:11.794274 INFO Failed to check ring signature for tx <5879b37601799a3e5d27f8e821c487d0810f421a1a8f60b48b3e1244471b5bb3>
22:06:11.822124 INFO Wrong index in transaction inputs: 1969, expected maximum 1966
22:06:11.822280 INFO Failed to get output keys for tx with amount = 0.000000000080000000 and count indexes 1
22:06:11.822382 INFO Failed to check ring signature for tx <ff47a5ebca3c1b131a9f88976a7c2b13bab25b925de789401eaac9306a310d13>

maybe the same/a similar error like Eurobit has since a few days -> maybe you can get help from Eurobit-devs?

[egano]

seems like the blockchain's "broken".
...doesn't get new blocks since a while now (hangin on block #19456).
Also getting an error in daemon like:

22:06:11.742850 INFO Wrong index in transaction inputs: 2007, expected maximum 2006
22:06:11.743141 INFO Failed to get output keys for tx with amount = 0.000000000000004000 and count indexes 1
22:06:11.743513 INFO Failed to check ring signature for tx <1fbedc7a8d6e044ff3b5562a03289e7f95c869af66316e56de5a75183243d1a2>
22:06:11.750720 INFO Wrong index in transaction inputs: 1965, expected maximum 1963
22:06:11.750976 INFO Failed to get output keys for tx with amount = 0.000000000000030000 and count indexes 1
22:06:11.751343 INFO Failed to check ring signature for tx <8833aa4a5650143a457ee4b1c1cc2a547274713a08a5be46c7adb7853f1f148e>
22:06:11.756499 INFO Wrong index in transaction inputs: 1973, expected maximum 1970
22:06:11.756678 INFO Failed to get output keys for tx with amount = 0.000000000070000000 and count indexes 1
22:06:11.756997 INFO Failed to check ring signature for tx <084581968d9c72c66509ebc2869b1c77d758eb02057cd0148d65c3aad884c20f>
22:06:11.793562 INFO Wrong index in transaction inputs: 93, expected maximum 92
22:06:11.793828 INFO Failed to get output keys for tx with amount = 0.000000060000000000 and count indexes 1
22:06:11.794274 INFO Failed to check ring signature for tx <5879b37601799a3e5d27f8e821c487d0810f421a1a8f60b48b3e1244471b5bb3>
22:06:11.822124 INFO Wrong index in transaction inputs: 1969, expected maximum 1966
22:06:11.822280 INFO Failed to get output keys for tx with amount = 0.000000000080000000 and count indexes 1
22:06:11.822382 INFO Failed to check ring signature for tx <ff47a5ebca3c1b131a9f88976a7c2b13bab25b925de789401eaac9306a310d13>

maybe the same/a similar error like Eurobit has since a few days -> maybe you can get help from Eurobit-devs?

One of our nodes has the same issue, the other is higher (19493) so trying to resync. Will look to Eurobit to find out more about invalid transactions, but if one of the chains wins in the end, there will be just an orphaned branch left behind.

[MrCross]

23:57:43.435648 INFO SYNCHRONIZATION started
23:57:44.173695 INFO Block <2b2f5b40dc0fa485b4576546f51bcfe5db267bd63311843f25e1a7d511ede474> is too big: 24319 bytes, exptected no more than 24276 bytes

[egano]

23:57:43.435648 INFO SYNCHRONIZATION started
23:57:44.173695 INFO Block <2b2f5b40dc0fa485b4576546f51bcfe5db267bd63311843f25e1a7d511ede474> is too big: 24319 bytes, exptected no more than 24276 bytes

An intentional stress test was done around block 19450 and further. The network was flooded with hundreds of transactions per block, consolidating inputs mined in thousands transactions earlier. It seems that the daemon accepts some malformed inputs and even worse accepts such block broadcasted from another node if it has some matching inputs in mempool.
The only workaround to this until it is further investigated is to resync and mine new branch if your height is increasing and is above 19488, and do daily backups of blockchain database until a reasonable fix is released.

[MrCross]

just to be sure, that I'm on the right blockchain: whats the current height (bc_height)?

[egano]

just to be sure, that I'm on the right blockchain: whats the current height (bc_height)?

Current height 20561. Every day one of our nodes is reset to second latest backup to catch any sync issues early.

[Atix]

@egano

Hey, I've set up a pool but I can't get the payouts working properly because of the decimals. I had a look at CryptonoteConfig.h but still no luck. Other than that the pool works. What did I do wrong?

Code:

2018-01-12 19:40:07 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Wrong amount"}
2018-01-12 19:40:07 [payments] Payments failed to send to {"amount":106952000000000,"address":"abcd1w....

Code:

[wallet abcd1w]: pool wallet
Unknown command: pool
[wallet abcd1w]: balance
available balance: 0.000097150672525004, locked amount: 0.000005664308578258

config:

Code:

"coinUnits": 1000000000000000000 // Minimum units in a single coin, see COIN constant in DAEMON_CODE/src/cryptonote_config.h - No coin constant
"transferFee": 50000000,
"minPayment": 1000000000,
"maxTransactionAmount": 500000000000000,
"denomination": 1000000000 //truncate to this precision and store remainder

[egano]

@egano

Hey, I've set up a pool but I can't get the payouts working properly because of the decimals. I had a look at CryptonoteConfig.h but still no luck. Other than that the pool works. What did I do wrong?

Code:

2018-01-12 19:40:07 [payments] Error with transfer RPC request to wallet daemon {"code":-4,"message":"Wrong amount"}
2018-01-12 19:40:07 [payments] Payments failed to send to {"amount":106952000000000,"address":"abcd1w....

Code:

[wallet abcd1w]: pool wallet
Unknown command: pool
[wallet abcd1w]: balance
available balance: 0.000097150672525004, locked amount: 0.000005664308578258

config:

Code:

"coinUnits": 1000000000000000000 // Minimum units in a single coin, see COIN constant in DAEMON_CODE/src/cryptonote_config.h - No coin constant
"transferFee": 50000000,
"minPayment": 1000000000,
"maxTransactionAmount": 500000000000000,
"denomination": 1000000000 //truncate to this precision and store remainder

Solving the same challenge in order to make our pool working correctly.
Try sending manually the amount shifted by 18 decimal places to the wallet daemon to see what you receive. After that values in config can be changed accordingly.
Independently we test our pool and once working as expected it will be released here including config.
During testing the Wrong anount error always meant insufficient balance older than 60 blocks.