Topic: Goldo - Soldo Fork (Read 18089 times)
Goldo SWAP is started - https://soldo.in/app/xoldo/
Buenos dias and buongiorno @here!
XOLDO updates @ FRESHMEAT ;-)
BTW, SWAP procedure will be started 01-MAR-2020.
Stay tuned!
XOLDO updates @ FRESHMEAT ;-)
BTW, SWAP procedure will be started 01-MAR-2020.
Stay tuned!
Argon2 memory target tesitng is finished.
Capitalism is win, we will use 512KB of memory in PoW function.
Capitalism is win, we will use 512KB of memory in PoW function.
The choice of the target from my point of view has come down to two options - 512 and 1024.
256 is clearly scaled 2 times 512, there is absolutely no difference between them, only twice more beautiful digits.
Above 1024, it is also meaningless to consider the same scaling twice.
But the difference between 1024 and 512 is fundamental.
1024
One computer - one voice, as Satoshi bequeathed.
The speed almost does not depend on the type and number of processors and cores in the computer.
The maximum speed is achieved with a minimum processor load, it is convenient to mine in parallel with the main work.
A good option for mining in the office network.
512
Who spends resources - that one wins.
The number of hardware cores in the computer plays a crucial role.
The more cores, the higher the hashrate.
Maximum speed is reached with maximum CPU load.
Mine profitable only on dedicated servers with a large number of cores.
Ideal for powerful modern servers with free resources.
Now we have to choose - we are voting for socialism (equality in income for all) or capitalism (the more expenses - the higher the income).
256 is clearly scaled 2 times 512, there is absolutely no difference between them, only twice more beautiful digits.
Above 1024, it is also meaningless to consider the same scaling twice.
But the difference between 1024 and 512 is fundamental.
1024
One computer - one voice, as Satoshi bequeathed.
The speed almost does not depend on the type and number of processors and cores in the computer.
The maximum speed is achieved with a minimum processor load, it is convenient to mine in parallel with the main work.
A good option for mining in the office network.
512
Who spends resources - that one wins.
The number of hardware cores in the computer plays a crucial role.
The more cores, the higher the hashrate.
Maximum speed is reached with maximum CPU load.
Mine profitable only on dedicated servers with a large number of cores.
Ideal for powerful modern servers with free resources.
Now we have to choose - we are voting for socialism (equality in income for all) or capitalism (the more expenses - the higher the income).
So you would say that RAM and other IO-hardware is not possible to buy more? Instead of forcing people to buy more CPUs, you'll just force them to buy more RAM, which might be a horrible idea, considering the shortage we already have. Seriously, a huge number of people is pissed at cryptocurrencies because they played a huge part in creating said shortage. I doubt that leveraging that will help.
Secondly, whats the advantage of Argon2d (i and id are useless for cryptocurrency, compared to d) compared to Ethash? I assume you wanted to have that CPU-only algorithm because many people want that so its great.
Well, thats your choice, while many people would disagree, there also are many who agree, so you certainly found yourself a nieche.
But thats not the point, Argon2d is horribly slow both for verification and for the miner if you want to have a decent security. On the other hand, assymetric algorithms such as RandomX, Ethash or SquashPoW work by forcing the miner to run a huge and ASIC-resistant scratchpad in RAM while you only need to use 64MB on a verifying node.
Since this has been a long block of text, let me ask that question again - whats the advantage of your Argon2d variant compared to any of the algorithms mentioned above?
Lastly, your whole assumption is faulty. You can always buy more RAM, you can always outsource your RAM-usage to a GPU and, even worse for you, you can put your HBM2.1 RAM directly on the CPU. Therefore, if you invest 10kUSD on an Arria FPGA, you will have significantly, more specific, exponentially, more power per USD than if you would use a common Xeon + RAM combination. Additionally the FPGA is ARM and shouldnt run at more than a hundred watts.
If you really are interested in fair distribution, you should take a look at Proof of Stake. The reason why I say this is explained in this post: https://hackernoon.com/consensus-mechanisms-explained-pow-vs-pos-89951c66ae10
The choice of the target from my point of view has come down to two options - 512 and 1024.
256 is clearly scaled 2 times 512, there is absolutely no difference between them, only twice more beautiful digits.
Above 1024, it is also meaningless to consider the same scaling twice.
But the difference between 1024 and 512 is fundamental.
1024
One computer - one voice, as Satoshi bequeathed.
The speed almost does not depend on the type and number of processors and cores in the computer.
The maximum speed is achieved with a minimum processor load, it is convenient to mine in parallel with the main work.
A good option for mining in the office network.
512
Who spends resources - that one wins.
The number of hardware cores in the computer plays a crucial role.
The more cores, the higher the hashrate.
Maximum speed is reached with maximum CPU load.
Mine profitable only on dedicated servers with a large number of cores.
Ideal for powerful modern servers with free resources.
Now we have to choose - we are voting for socialism (equality in income for all) or capitalism (the more expenses - the higher the income).
256 is clearly scaled 2 times 512, there is absolutely no difference between them, only twice more beautiful digits.
Above 1024, it is also meaningless to consider the same scaling twice.
But the difference between 1024 and 512 is fundamental.
1024
One computer - one voice, as Satoshi bequeathed.
The speed almost does not depend on the type and number of processors and cores in the computer.
The maximum speed is achieved with a minimum processor load, it is convenient to mine in parallel with the main work.
A good option for mining in the office network.
512
Who spends resources - that one wins.
The number of hardware cores in the computer plays a crucial role.
The more cores, the higher the hashrate.
Maximum speed is reached with maximum CPU load.
Mine profitable only on dedicated servers with a large number of cores.
Ideal for powerful modern servers with free resources.
Now we have to choose - we are voting for socialism (equality in income for all) or capitalism (the more expenses - the higher the income).
Test daemons - http://ftp://soldo:[email protected]/LastBuilds/qcc/
So, the results of testing Argon2d.
Initially, the idea was to take a target in 1G RAM to protect against botnets.
However, in real mining with such a goal, 1 hash is calculated for a few seconds and the system falls into a coma.
Therefore, smaller targets were tested - from 64MB and down twice at each iteration.
The results are somewhat confusing, but the conclusions are as follows:
- to protect against botnets Argon will not work, because RAM consumption is not too large;
- on large targets, powerful processors do not exceed low-power ones;
- CPU load increases linearly with the increase in the number of threads and does not depend on tagret, except for tiny ones;
- on tiny targets powerful processors begin to dominate.
Please express your thoughts, what size of target we will take in PoW ...
Initially, the idea was to take a target in 1G RAM to protect against botnets.
However, in real mining with such a goal, 1 hash is calculated for a few seconds and the system falls into a coma.
Therefore, smaller targets were tested - from 64MB and down twice at each iteration.
The results are somewhat confusing, but the conclusions are as follows:
- to protect against botnets Argon will not work, because RAM consumption is not too large;
- on large targets, powerful processors do not exceed low-power ones;
- CPU load increases linearly with the increase in the number of threads and does not depend on tagret, except for tiny ones;
- on tiny targets powerful processors begin to dominate.
Please express your thoughts, what size of target we will take in PoW ...
Goldo support is finished.
Explorer could be found @ http://xex.soldo.in/
Xoldo was forked @ block# 2368888.
Guys,
I should to notify that tomorrow I’ll fininsh my support of Goldo.
Exactly a year, as I promised while the fork, I supported the network and updated the applications code.
Now anyone can become the owner of this project.
The code for Goldo apps will be moved to a separate account on Github.
The new owner will get full access to this account.
Write me if you want manage the Goldo project!!!
The launch and support of Goldo has become an important milestone, however, time to go further.
I firmly learned the lessons during the fork of Soldo and managing it.
My principle since that time is simple - never touch a live coin.
Let it live or die by itself, without my participation.
Therefore, I am launching a fork of Goldo soon.
Maybe it will be Soldo Argento, as it was originally planned, and maybe Holdo - name does not matter.
The fork will initially restrict emission to 6M coins.
It may also be held a denomination 10 times, but this has not yet been decided.
The name and ticker will be changed to avoid confusion.
Network settings will also be changed to avoid collisions.
After the supply will reach 6M, a new coin swap will be launched in order to:
- change the algorithm of the PoW function to ARGON2 or Balloon, it is possible to combine them with light versions of CryptoNight;
- elimination of blockchain bloat;
- increase the time of the block and, accordingly, the difficulty 5-15 times, an exact number has not yet been approved;
- increase rewards to miners;
- denominations, although it is also questionable;
New coin will have a premine of 6M coins.
This coins will be exchanged to current 6M of Goldo supply 1:1, or in a denomination's proportion.
Lottery will remain unchanged.
I also want to note that after the final approval of the coin's parameters and its launch, the basic parameters will not change anymore.
This I can guarantee, because unlike the launch of Soldo, I work not for hire, but on my own.
Thus, I control all aspects of this project.
Further discussion about new coins and current coins evolving will take place at the https://discord.gg/s5EpfGa Discord chat.
I should to notify that tomorrow I’ll fininsh my support of Goldo.
Exactly a year, as I promised while the fork, I supported the network and updated the applications code.
Now anyone can become the owner of this project.
The code for Goldo apps will be moved to a separate account on Github.
The new owner will get full access to this account.
Write me if you want manage the Goldo project!!!
The launch and support of Goldo has become an important milestone, however, time to go further.
I firmly learned the lessons during the fork of Soldo and managing it.
My principle since that time is simple - never touch a live coin.
Let it live or die by itself, without my participation.
Therefore, I am launching a fork of Goldo soon.
Maybe it will be Soldo Argento, as it was originally planned, and maybe Holdo - name does not matter.
The fork will initially restrict emission to 6M coins.
It may also be held a denomination 10 times, but this has not yet been decided.
The name and ticker will be changed to avoid confusion.
Network settings will also be changed to avoid collisions.
After the supply will reach 6M, a new coin swap will be launched in order to:
- change the algorithm of the PoW function to ARGON2 or Balloon, it is possible to combine them with light versions of CryptoNight;
- elimination of blockchain bloat;
- increase the time of the block and, accordingly, the difficulty 5-15 times, an exact number has not yet been approved;
- increase rewards to miners;
- denominations, although it is also questionable;
New coin will have a premine of 6M coins.
This coins will be exchanged to current 6M of Goldo supply 1:1, or in a denomination's proportion.
Lottery will remain unchanged.
I also want to note that after the final approval of the coin's parameters and its launch, the basic parameters will not change anymore.
This I can guarantee, because unlike the launch of Soldo, I work not for hire, but on my own.
Thus, I control all aspects of this project.
Further discussion about new coins and current coins evolving will take place at the https://discord.gg/s5EpfGa Discord chat.
Guys,
Tomorrow I will finish to support Goldo.
Goldo code will be moved to a separate Github account.
Anyone who wants to become the owner of this project can contact me, and I will give him access to this account.
Discussion will be continued @ https://discord.gg/s5EpfGa
the wallet does not connect
Sent a request for listing https://fcryptobank.com/
Nope.
Blockchain is solid, seeds are on, transactions superfast.
Blockchain is solid, seeds are on, transactions superfast.
So this project died ?
Hello Dev. Thanks for your support.
I just tried to compile new daemon on Amazon Ubuntu 16.04 VM and got error provided down bellow.
BTW latest SLD daemon was compiled successfully on this server.
[ 52%] Built target BlockchainExplorer
make[3]: Entering directory '/home/ubuntu/goldo/build/release'
Scanning dependencies of target CryptoNoteCore
make[3]: Leaving directory '/home/ubuntu/goldo/build/release'
make[3]: Entering directory '/home/ubuntu/goldo/build/release'
[ 53%] Building CXX object src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Difficulty.cpp.o
[ 53%] Building CXX object src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o
/home/ubuntu/goldo/src/CryptoNoteCore/Core.cpp:1065:1: error: expected ‘}’ at end of input
}
^
src/CMakeFiles/CryptoNoteCore.dir/build.make:86: recipe for target 'src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o' failed
make[3]: *** [src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o] Error 1
make[3]: Leaving directory '/home/ubuntu/goldo/build/release'
CMakeFiles/Makefile2:796: recipe for target 'src/CMakeFiles/CryptoNoteCore.dir/all' failed
make[2]: *** [src/CMakeFiles/CryptoNoteCore.dir/all] Error 2
make[2]: Leaving directory '/home/ubuntu/goldo/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/ubuntu/goldo/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2
I just tried to compile new daemon on Amazon Ubuntu 16.04 VM and got error provided down bellow.
BTW latest SLD daemon was compiled successfully on this server.
[ 52%] Built target BlockchainExplorer
make[3]: Entering directory '/home/ubuntu/goldo/build/release'
Scanning dependencies of target CryptoNoteCore
make[3]: Leaving directory '/home/ubuntu/goldo/build/release'
make[3]: Entering directory '/home/ubuntu/goldo/build/release'
[ 53%] Building CXX object src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Difficulty.cpp.o
[ 53%] Building CXX object src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o
/home/ubuntu/goldo/src/CryptoNoteCore/Core.cpp:1065:1: error: expected ‘}’ at end of input
}
^
src/CMakeFiles/CryptoNoteCore.dir/build.make:86: recipe for target 'src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o' failed
make[3]: *** [src/CMakeFiles/CryptoNoteCore.dir/CryptoNoteCore/Core.cpp.o] Error 1
make[3]: Leaving directory '/home/ubuntu/goldo/build/release'
CMakeFiles/Makefile2:796: recipe for target 'src/CMakeFiles/CryptoNoteCore.dir/all' failed
make[2]: *** [src/CMakeFiles/CryptoNoteCore.dir/all] Error 2
make[2]: Leaving directory '/home/ubuntu/goldo/build/release'
Makefile:94: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/ubuntu/goldo/build/release'
Makefile:20: recipe for target 'build-release' failed
make: *** [build-release] Error 2
New build is ready, both GUI and CLI apps updated.
Update contains all of the latest code fixes from Soldo code base Build #52 from Dec-18 - ATTACK 51% protection, read-only-wallets, daemon's public mode, new commands in daemon, etc...
Sources commited to Github, binaries released as well.
https://github.com/monselice/goldo/releases
Good luck!
Update contains all of the latest code fixes from Soldo code base Build #52 from Dec-18 - ATTACK 51% protection, read-only-wallets, daemon's public mode, new commands in daemon, etc...
Sources commited to Github, binaries released as well.
https://github.com/monselice/goldo/releases
Good luck!
New build is nearby.
It will have 51% ATTACK preventing code.
It will have 51% ATTACK preventing code.
Jump to: