[ANN][AVE][ICO] Avesta PoW 10s blocktime+accountnumbers+Inheritance+Private+App

[Mark_l]

please add gpu mining

**What follows is just my personal opinion, you may have a different one and that's cool**

Please dont add GPU mining  

As soon as GPU mining is added everyone will mine with GPU's, thus nullifying the benefit of mining with GPU's.

If they leave it as CPU only then we can have a coin we can profitably mine with our CPU's while our GPU's do other things, like mining coins that you can't mine profitably with your CPU because people can mine them with GPU's.

Also, as this coin is targeted at less developed parts of the world why not give someone who has accecss to a last gen CPU (e.g. Lynnfield i5-750 or similar) but doesn't have access to a few RX 580's \ GTX 1070's a chance to mine?

Without GPU's it might even be profitable to mine on some mobile devices.....?

This is probably my naivety talking, but I also like the thought that all those mining rigs out there with 6x RX 580's \ GTX 1070's will absolutely suck at mining this coin if it's CPU only. Normally you'd stick the cheapest CPU you can in a mining rig and max the GPU's.

It's the hobbyists with a couple of GPU's and a decent processor who use thier machines for gaming and the like that will excel and mining this if It's CPU only. They are the ones that will have powerful processors in thier machines.

After all, isn't that what crypto's all about? De-centralised block processing, the more de-centralised the better  

[1715085333]

1715085333

[1715085333]

1715085333

[1715085333]

1715085333

[1715085333]

1715085333

[1715085333]

1715085333

[jlaranjeiro]

Hi guys, I am since yesterday to sync the node to start mining, but it seems now I am stuck at block 660244, are you having the same issue? DEVs are you trying to solve the problem?

[eliastt]

Ok. There is something wrong with the windows binaries.

Now the miner stopped crashing but the avestad.exe crashes randomly with this error:

Assertion failed: found != chainsLeaves.end()


The worst part is that it corrupts the blockchain DB and then I have to rebuild it.

[jlaranjeiro]

For the DEVs:

Well I finally started mining, first issue I found:
- I have a ryzen 1800x with 16 threads and 16MB L3, since this is a cryptonight algo, I should be using one thread per core and I am using both, becoming inefficient
- I had to decrease the priority of the miner on Task manager to Low, or else my GPUs stop mining, but even at low I have a decrease in 5% less hash power on GPUs, I would say the problem is the use of 100% of the processor
- Even using 100% processor is 20% cooler than normal, miner maybe is not yet optimized (should you start a pool to us use for example XMR stak?)
- There is any information we could get from the miner ( stats, hashes, ping, etc?)

[icocash]

Sounds interesting project

[pattanagla]

my error

2018-Feb-12 22:34:03.681841 ERROR   Corrupted blockchain. Block with index 660640 and hash 6e9b1fbfb16fc9d850a88be1e09ecfd4c5fd8298ef2a438a90d3c64e3bba3bc8 has previous block hash 82c1c5089011dc482c9a8f1be53c4db300e0dfb8cb0d19a4e380b985784953a4, but parent has hash a9b329f454419c4e9300cdfcbd1768a9e2f5319568bf30d15ac2cdc2eff62e64. Resynchronize your daemon please.
SwappedVector cache hits: 1, misses: 21 (95.45%)
SwappedVector cache hits: 1, misses: 21 (95.45%)
2018-Feb-12 22:34:03.694857 INFO    Closing DB.

p.s. Now I del all db in %appdata% and restart.It's ok.

[cranefist]

I put up a Avesta discord channel if someone is interested in joining, its not official as i'm not part of Avesta. But maybe its useful for gathering & spreading information about this project, and how to mine it efficiently.

https://discord.gg/AJRGAWU

At the moment, this is the largest Avesta discord channel in the known universe!

#world-domination

[Mark_l]

Amongst the other cool things they have been up to, Avesta has applied for listing on Binance..

https://blog.avesta.io/avesta-cryptocurrency-news-development-strides-new-partnerships/

I put up a Avesta discord channel

Cool, registered  

p.s. Now I del all db in %appdata% and restart.It's ok.

I have two machine on the go, and Avestad and the miner installed on both.

When one of the copies of Avestad goes out I use the command line to point both miners at the remaining working node whilst the broiken one syncs.

It's also worth taking a copy of the DB folder (with the Avestad process stopped) every coupel of days. Then if it corrupts you can start from a couple of days ago instead of re-syncing from scratch.

- I have a ryzen 1800x with 16 threads and 16MB L3, since this is a cryptonight algo, I should be using one thread per core and I am using both, becoming inefficient
- I had to decrease the priority of the miner on Task manager to Low, or else my GPUs stop mining, but even at low I have a decrease in 5% less hash power on GPUs, I would say the problem is the use of 100% of the processor
- Even using 100% processor is 20% cooler than normal, miner maybe is not yet optimized (should you start a pool to us use for example XMR stak?)
- There is any information we could get from the miner ( stats, hashes, ping, etc?)

Nice CPU, Ryzen 1600 @ 4Ghz here. Works well but those extra couple of cores would be nice.

Have the same problem with GPU minng at the same time, and even on 'below normal' the whole PC freezes up for about 10->15 seconds every once in a while with the miner running.

The whole network will operate like a pool, 1.9 AVE to the miner who found the block and 1.0 AVE split amongst all other miners. It's a very cool system.

'--log-level 5' is the best your going to get for now. Although.. in the post linked above they do mention releasing 'mining stats'...??

[Mark_l]

Has anyone else got this issue?

Both my copies of Avestad stopped working and neither will sync. I have tried restoring an earlier version of the DB folder, and also clearing the DB folder and syncing from scratch.

Getting this error:

2018-Feb-13 19:55:36.886911 INFO    Importing blocks from blockchain storage
2018-Feb-13 19:55:37.121324 ERROR   Corrupted blockchain. Block with index 655938 and hash 2c520bdbad92843f28954aa68903e412dad8bcda075f58ca79716a129040cc38 has previous block hash f1549dc15819809ff10fd61a235b8a516501d3b5683b87876e1d2e8e8544796d, but parent has hash efc137c090e0ee0a6a3aeec25a4d742c537bc11dc7547d4ee685963e45c0de71. Resynchronize your daemon please.
SwappedVector cache hits: 1, misses: 21 (95.45%)
SwappedVector cache hits: 1, misses: 21 (95.45%)
2018-Feb-13 19:55:37.136943 INFO    Closing DB.
2018-Feb-13 19:55:37.152583 ERROR   Exception: Blockchain storage is corrupted

[jlaranjeiro]

Has anyone else got this issue?

Both my copies of Avestad stopped working and neither will sync. I have tried restoring an earlier version of the DB folder, and also clearing the DB folder and syncing from scratch.

Getting this error:

2018-Feb-13 19:55:36.886911 INFO    Importing blocks from blockchain storage
2018-Feb-13 19:55:37.121324 ERROR   Corrupted blockchain. Block with index 655938 and hash 2c520bdbad92843f28954aa68903e412dad8bcda075f58ca79716a129040cc38 has previous block hash f1549dc15819809ff10fd61a235b8a516501d3b5683b87876e1d2e8e8544796d, but parent has hash efc137c090e0ee0a6a3aeec25a4d742c537bc11dc7547d4ee685963e45c0de71. Resynchronize your daemon please.
SwappedVector cache hits: 1, misses: 21 (95.45%)
SwappedVector cache hits: 1, misses: 21 (95.45%)
2018-Feb-13 19:55:37.136943 INFO    Closing DB.
2018-Feb-13 19:55:37.152583 ERROR   Exception: Blockchain storage is corrupted

This beta miner is a really pain, I already rebuild 3 times today my Daemons.

I advise you to delete all data and then resynchronize and save it at the end to a safe place, so Everytime you need to rebuild you only lose a few minutes to copy the files and resynchronize. Maybe the experts have a better advise

[Mark_l]

This beta miner is a really pain, I already rebuild 3 times today my Daemons.

I advise you to delete all data and then resynchronize and save it at the end to a safe place, so Everytime you need to rebuild you only lose a few minutes to copy the files and resynchronize. Maybe the experts have a better advise Smiley

Hi,

Thanks for the reply. That's what I do, the problem is that the only backup I have was from before block 655938.. and every time either of my machines try to sync past block 655938 Avestad crashes.

I have tried a complete cleardown and re-sync on both machines but they get stuck in the same place (block 655938).

Completely stuffed at the moment  

[jlaranjeiro]

This beta miner is a really pain, I already rebuild 3 times today my Daemons.

I advise you to delete all data and then resynchronize and save it at the end to a safe place, so Everytime you need to rebuild you only lose a few minutes to copy the files and resynchronize. Maybe the experts have a better advise Smiley

Hi,

Thanks for the reply. That's what I do, the problem is that the only backup I have was from before block 655938.. and every time either of my machines try to sync past block 655938 Avestad crashes.

I have tried a complete cleardown and re-sync on both machines but they get stuck in the same place (block 655938).

Completely stuffed at the moment  

When I first try to sync my daemon I had a similar problem on the block 660240 (I think). But now if I remember, the problem was solved by himself a few hours later.

Maybe this is a problem with the node you are connecting to, try check on daemon which one you are connected, since I remember before coming to bed, that there is one node out of sync or not possible to connect, something like that, maybe that's the problem.

[jannoi]

Whomever missed the Links:

AVE explorer: https://app.avesta.io/avesta-explorer/v2
AVE blog: https://blog.avesta.io/
Downloads: https://mega.nz/#F!KAY3RaQR!YoxUnUJi-LnA9kCZo8ZKfg

[jlaranjeiro]

Some more considerations for the DEVs based on my very short experience:

- Even without knowing the hash rate right now, I would assume that comparing to other miners (XMR stak or Claymore) this miner does not yet reach its maximum capabilities, but more important I notice an increase of power consumption of circa 40% on my cpu, with the same specs() used by Stak for example.

- On the Daemon, it is not possible to save, the only command that saves is exiting, since it freezes and crashes every hour, and I usually need to rebuild the DB, maybe this could mitigate the problem, I know we are early adopters, but i am basically sitting in front of my computer looking to the miner and waiting him to crash, is quite stressfull  

- How can we miners help you more by giving you more inputs, which information are you looking for?

- ( I know almost nothing about coding, just want to give you my input, hoping you can improve things)

- Please improve your communications channels and bring us miners more information. I know you already have a broad support, but I personally believe that the miners will help to spread the word and makes this coin big, as I think it deserves to be.

- Improve your Readme file at the miner with more information, it will help people.

[Mark_l]

Got the client working again after conversing with the team. Aparenty it's a known issue which is fixed in the new version of the miner and client.

PS.. now, come close because I don't want to say this too loud or loads of people will hear.. but a new miner and client are on the way in 'the next few days'.. but don't tell anyone I told you   I'm quite excited about this because in thier last blog post they mentioned  stats for miners.. maybe the miner is about to display has rates etc???

Even without knowing the hash rate right now, I would assume that comparing to other miners (XMR stak or Claymore) this miner does not yet reach its maximum capabilities, but more important I notice an increase of power consumption of circa 40% on my cpu, with the same specs(Huh) used by Stak for example.

Totally agree with everything you have said, but just wanted to point out one thing relating to this bit.

Seeing as we are ALL using the same miner for this coin, the fact that it is a bit inefficient doesn't matter to much. We are all using a little more power than we need too and we are all hasing at a sub-optimal rate. The % split of rewards is therefore exactly the same as if the miner was 100% efficient. It's a wonderful, beautiful and all around amazing level playing field at the moment 

And, if I understand this correctly, as long as the difficulty is >1 then the chain has more hasing power than it needs so an extra few % right now from each miner doesnt really matter to much (<- please correct me on this)

[jlaranjeiro]

Seeing as we are ALL using the same miner for this coin, the fact that it is a bit inefficient doesn't matter to much. We are all using a little more power than we need too and we are all hasing at a sub-optimal rate. The % split of rewards is therefore exactly the same as if the miner was 100% efficient. It's a wonderful, beautiful and all around amazing level playing field at the moment 

And, if I understand this correctly, as long as the difficulty is >1 then the chain has more hasing power than it needs so an extra few % right now from each miner doesnt really matter to much (<- please correct me on this)

No, you are right, I just want to point that in future 10 or 20 Watts/hour more could be a big diference, for those who are mining.

If a new miner is actually coming if I may I would also to add some features if possible:

- Hash rate ( instant and last 1 minute and 15 minutes)
- Number of found blocks
- Number of rejected blocks
- ping time
(for me this are the most important, but if you want to add more information, I am not against !)

[Mark_l]

- Hash rate ( instant and last 1 minute and 15 minutes)
- Number of found blocks
- Number of rejected blocks
- ping time

+ The ability to set CPU core affinity 

[jannoi]

Seeing as we are ALL using the same miner for this coin, the fact that it is a bit inefficient doesn't matter to much. We are all using a little more power than we need too and we are all hasing at a sub-optimal rate. The % split of rewards is therefore exactly the same as if the miner was 100% efficient. It's a wonderful, beautiful and all around amazing level playing field at the moment 

And, if I understand this correctly, as long as the difficulty is >1 then the chain has more hasing power than it needs so an extra few % right now from each miner doesnt really matter to much (<- please correct me on this)

No, you are right, I just want to point that in future 10 or 20 Watts/hour more could be a big diference, for those who are mining.

If a new miner is actually coming if I may I would also to add some features if possible:

- Hash rate ( instant and last 1 minute and 15 minutes)
- Number of found blocks
- Number of rejected blocks
- ping time
(for me this are the most important, but if you want to add more information, I am not against !)

Noted
And yes, power efficiency is important.

+ The ability to set CPU core affinity 

You can set the number of threads with --threads [number]

[ladozhskiy1995]

give us more info about  this project,something new for me i want to closely follow it

[jannoi]

give us more info about  this project,something new for me i want to closely follow it

Please check our blog, or follow us on Social media.

http://blog.avesta.io/