Before the release of the new explorer block, it left 12 days
Is the richlist in it? 
Topic: [ANN] [CRP] | cranepay | CPU Only | YesPoWer | True Cryptocurrency - page 23. (Read 47597 times)
July 13, 2018, 04:35:30 PM
July 13, 2018, 04:25:14 PM
Before the release of the new explorer block, it left 12 days
July 13, 2018, 01:00:53 PM
you can download blocks on https://cryply.download/users/Cryply
Are you guys kidding? I wanted to start with this coin and downloaded the wallet, but it syncs like forever (more than 20 hours for 4 weeks and now stuck at 15 weeks remaining). So apparently there is a download for the CRP blocks to speed this up/make this possible, but you have to PAY WITH CRP for the download? How in the blue hell am I supposed to do that without a syncing wallet?This is absolutely ridiculous. You deliberately hamper newcomers (who are willing to support your blockchain by starting a node) for the profit of half a cent? You should seriously rethink your business strategy there.
try this - http://yenten-pool.ml/faucet-cryply/blocks.zip
Free limit increased to 300MB
https://cryply.download/users/cryply
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
July 13, 2018, 12:46:21 PM
For a week now, the mining of cryply
Very satisfied, but the laptop does not lags.
Cryply price only goes up.
Happy mining =)
Very satisfied, but the laptop does not lags.
Cryply price only goes up.
Happy mining =)
July 13, 2018, 12:36:11 PM
On https://cryply.download/users/Cryply the limit to 300 megabytes
July 13, 2018, 01:22:21 AM
And it won't support 
Cryply is only one CPU coin for now.
Cryply is only one CPU coin for now.
The CPU COIN!
July 13, 2018, 12:16:51 AM
And it won't support
Cryply is only one CPU coin for now.
Cryply is only one CPU coin for now.
July 12, 2018, 04:08:52 PM
yespower - proof-of-work (PoW) scheme
http://www.openwall.com/yespower/
yespower is a proof-of-work (PoW) focused fork of yescrypt, which in turn builds upon scrypt. While yescrypt is a password-based key derivation function (KDF) and password hashing scheme, and thus is meant for processing passwords, yespower is meant for processing trial inputs such as block headers (including nonces) in PoW-based blockchains.
Download (release notes):
yespower 1.0.0 and its signature
This and (eventually) older versions of yespower will also be available from the Openwall file archive. The source code of yespower may be browsed via CVSweb.
Follow this link for information on verifying the signatures.
We may help you integrate yespower into your software or online services. Please check out our services.
yespower consortium
Cryptocurrency projects that use yespower are expected to join the informal yespower consortium, which involves supporting the yespower project financially and having more of a say on its future direction. Without endorsing any of these projects in any way, we currently list the "consortium members" here so that the different cryptocurrency projects and their users know which projects are significantly supporting yespower upstream development (those listed here) and which don't (the rest). Currently, there's just one:
cryply.
Please contact us about joining the consortium.
Why or why not yespower?
Different proof-of-work schemes in existence vary in many aspects, including in friendliness to different types of hardware. There's demand for all sorts of hardware (un)friendliness in those - for different use cases and by different communities.
yespower in particular is designed to be CPU-friendly, GPU-unfriendly, and FPGA/ASIC-neutral. In other words, it's meant to be relatively efficient to compute on current CPUs and relatively inefficient on current GPUs. Unfortunately, being GPU-unfriendly also means that eventual FPGA and ASIC implementations will only compete with CPUs, and at least ASICs will win over the CPUs (FPGAs might not because of this market's peculiarities - large FPGAs are even more "over-priced" than large CPUs are), albeit by far not to the extent they did e.g. for Bitcoin and Litecoin.
There's a lot of talk about "ASIC resistance". What is (or should be) meant by that is limiting the advantage of specialized ASICs. While limiting the advantage at KDF to e.g. 10x and at password hashing to e.g. 100x (talking orders of magnitude here, in whatever terms) may be considered "ASIC resistant" (as compared to e.g. 100,000x we'd have without trying), similar improvement factors are practically not "ASIC resistant" for cryptocurrency mining where they can make all the difference between CPU mining being profitable and not. There might also exist in-between PoW use cases where moderate ASIC advantage is OK, such as with non-cryptocurrency and/or private/permissioned blockchains.
Thus, current yespower may be considered either a short-term choice (valid until one of its uses provides sufficient perceived incentive to likely result in specialized ASICs) or a deliberate choice of a pro-CPU, anti-GPU, moderately-pro-ASIC PoW scheme. It is also possible to respond to known improvements in future GPUs/implementations and/or to ASICs with new versions of yespower that users would need to switch to.
yespower versions
yespower includes optimized and specialized re-implementation of the obsolete yescrypt 0.5 (based off its first submission to Password Hashing Competition back in 2014) now re-released as yespower 0.5, and brand new proof-of-work specific variation known as yespower 1.0.
yespower 0.5 is intended as a compatible upgrade for cryptocurrencies that already use yescrypt 0.5 (providing a few percent speedup), and yespower 1.0 may be used as a further upgrade or a new choice of PoW by those and other cryptocurrencies and other projects.
There are many significant differences between yespower 0.5 and 1.0 under the hood, but the main user visible difference is yespower 1.0 greatly improving on GPU-unfriendliness in light of improvements seen in modern GPUs (up to and including NVIDIA Volta) and GPU implementations of yescrypt 0.5. This is achieved mostly through greater use of CPUs' L2 cache.
The version of algorithm to use is requested through parameters, allowing for both algorithms to co-exist in client and miner implementations (such as in preparation for a cryptocurrency hard-fork and/or supporting multiple cryptocurrencies in one program).
Thanks, very cognitively. http://www.openwall.com/yespower/
yespower is a proof-of-work (PoW) focused fork of yescrypt, which in turn builds upon scrypt. While yescrypt is a password-based key derivation function (KDF) and password hashing scheme, and thus is meant for processing passwords, yespower is meant for processing trial inputs such as block headers (including nonces) in PoW-based blockchains.
Download (release notes):
yespower 1.0.0 and its signature
This and (eventually) older versions of yespower will also be available from the Openwall file archive. The source code of yespower may be browsed via CVSweb.
Follow this link for information on verifying the signatures.
We may help you integrate yespower into your software or online services. Please check out our services.
yespower consortium
Cryptocurrency projects that use yespower are expected to join the informal yespower consortium, which involves supporting the yespower project financially and having more of a say on its future direction. Without endorsing any of these projects in any way, we currently list the "consortium members" here so that the different cryptocurrency projects and their users know which projects are significantly supporting yespower upstream development (those listed here) and which don't (the rest). Currently, there's just one:
cryply.
Please contact us about joining the consortium.
Why or why not yespower?
Different proof-of-work schemes in existence vary in many aspects, including in friendliness to different types of hardware. There's demand for all sorts of hardware (un)friendliness in those - for different use cases and by different communities.
yespower in particular is designed to be CPU-friendly, GPU-unfriendly, and FPGA/ASIC-neutral. In other words, it's meant to be relatively efficient to compute on current CPUs and relatively inefficient on current GPUs. Unfortunately, being GPU-unfriendly also means that eventual FPGA and ASIC implementations will only compete with CPUs, and at least ASICs will win over the CPUs (FPGAs might not because of this market's peculiarities - large FPGAs are even more "over-priced" than large CPUs are), albeit by far not to the extent they did e.g. for Bitcoin and Litecoin.
There's a lot of talk about "ASIC resistance". What is (or should be) meant by that is limiting the advantage of specialized ASICs. While limiting the advantage at KDF to e.g. 10x and at password hashing to e.g. 100x (talking orders of magnitude here, in whatever terms) may be considered "ASIC resistant" (as compared to e.g. 100,000x we'd have without trying), similar improvement factors are practically not "ASIC resistant" for cryptocurrency mining where they can make all the difference between CPU mining being profitable and not. There might also exist in-between PoW use cases where moderate ASIC advantage is OK, such as with non-cryptocurrency and/or private/permissioned blockchains.
Thus, current yespower may be considered either a short-term choice (valid until one of its uses provides sufficient perceived incentive to likely result in specialized ASICs) or a deliberate choice of a pro-CPU, anti-GPU, moderately-pro-ASIC PoW scheme. It is also possible to respond to known improvements in future GPUs/implementations and/or to ASICs with new versions of yespower that users would need to switch to.
yespower versions
yespower includes optimized and specialized re-implementation of the obsolete yescrypt 0.5 (based off its first submission to Password Hashing Competition back in 2014) now re-released as yespower 0.5, and brand new proof-of-work specific variation known as yespower 1.0.
yespower 0.5 is intended as a compatible upgrade for cryptocurrencies that already use yescrypt 0.5 (providing a few percent speedup), and yespower 1.0 may be used as a further upgrade or a new choice of PoW by those and other cryptocurrencies and other projects.
There are many significant differences between yespower 0.5 and 1.0 under the hood, but the main user visible difference is yespower 1.0 greatly improving on GPU-unfriendliness in light of improvements seen in modern GPUs (up to and including NVIDIA Volta) and GPU implementations of yescrypt 0.5. This is achieved mostly through greater use of CPUs' L2 cache.
The version of algorithm to use is requested through parameters, allowing for both algorithms to co-exist in client and miner implementations (such as in preparation for a cryptocurrency hard-fork and/or supporting multiple cryptocurrencies in one program).
In short we have 2-3 years mining without GPU's, ASICs?
I think that the year is at best. Further work is planned on the modification of the YesPoWer algorithm, we planned hardfork in 2020.
https://github.com/KlausT/ccminer/releases 8.22
added --hwmonitor option
Every minute or so you can see the temperature, the fan speed, the clocks and the power draw of each card
The Windows binaries are now using CUDA 9.2, but CUDA 8.0 is also available if 9.2 doesn't work for you.
New releases do not support YesPoWer!
[moderator's note: consecutive posts merged]
July 12, 2018, 03:59:07 PM
yespower - proof-of-work (PoW) scheme
http://www.openwall.com/yespower/
yespower is a proof-of-work (PoW) focused fork of yescrypt, which in turn builds upon scrypt. While yescrypt is a password-based key derivation function (KDF) and password hashing scheme, and thus is meant for processing passwords, yespower is meant for processing trial inputs such as block headers (including nonces) in PoW-based blockchains.
Download (release notes):
yespower 1.0.0 and its signature
This and (eventually) older versions of yespower will also be available from the Openwall file archive. The source code of yespower may be browsed via CVSweb.
Follow this link for information on verifying the signatures.
We may help you integrate yespower into your software or online services. Please check out our services.
yespower consortium
Cryptocurrency projects that use yespower are expected to join the informal yespower consortium, which involves supporting the yespower project financially and having more of a say on its future direction. Without endorsing any of these projects in any way, we currently list the "consortium members" here so that the different cryptocurrency projects and their users know which projects are significantly supporting yespower upstream development (those listed here) and which don't (the rest). Currently, there's just one:
cryply.
Please contact us about joining the consortium.
Why or why not yespower?
Different proof-of-work schemes in existence vary in many aspects, including in friendliness to different types of hardware. There's demand for all sorts of hardware (un)friendliness in those - for different use cases and by different communities.
yespower in particular is designed to be CPU-friendly, GPU-unfriendly, and FPGA/ASIC-neutral. In other words, it's meant to be relatively efficient to compute on current CPUs and relatively inefficient on current GPUs. Unfortunately, being GPU-unfriendly also means that eventual FPGA and ASIC implementations will only compete with CPUs, and at least ASICs will win over the CPUs (FPGAs might not because of this market's peculiarities - large FPGAs are even more "over-priced" than large CPUs are), albeit by far not to the extent they did e.g. for Bitcoin and Litecoin.
There's a lot of talk about "ASIC resistance". What is (or should be) meant by that is limiting the advantage of specialized ASICs. While limiting the advantage at KDF to e.g. 10x and at password hashing to e.g. 100x (talking orders of magnitude here, in whatever terms) may be considered "ASIC resistant" (as compared to e.g. 100,000x we'd have without trying), similar improvement factors are practically not "ASIC resistant" for cryptocurrency mining where they can make all the difference between CPU mining being profitable and not. There might also exist in-between PoW use cases where moderate ASIC advantage is OK, such as with non-cryptocurrency and/or private/permissioned blockchains.
Thus, current yespower may be considered either a short-term choice (valid until one of its uses provides sufficient perceived incentive to likely result in specialized ASICs) or a deliberate choice of a pro-CPU, anti-GPU, moderately-pro-ASIC PoW scheme. It is also possible to respond to known improvements in future GPUs/implementations and/or to ASICs with new versions of yespower that users would need to switch to.
yespower versions
yespower includes optimized and specialized re-implementation of the obsolete yescrypt 0.5 (based off its first submission to Password Hashing Competition back in 2014) now re-released as yespower 0.5, and brand new proof-of-work specific variation known as yespower 1.0.
yespower 0.5 is intended as a compatible upgrade for cryptocurrencies that already use yescrypt 0.5 (providing a few percent speedup), and yespower 1.0 may be used as a further upgrade or a new choice of PoW by those and other cryptocurrencies and other projects.
There are many significant differences between yespower 0.5 and 1.0 under the hood, but the main user visible difference is yespower 1.0 greatly improving on GPU-unfriendliness in light of improvements seen in modern GPUs (up to and including NVIDIA Volta) and GPU implementations of yescrypt 0.5. This is achieved mostly through greater use of CPUs' L2 cache.
The version of algorithm to use is requested through parameters, allowing for both algorithms to co-exist in client and miner implementations (such as in preparation for a cryptocurrency hard-fork and/or supporting multiple cryptocurrencies in one program).
Thanks, very cognitively. http://www.openwall.com/yespower/
yespower is a proof-of-work (PoW) focused fork of yescrypt, which in turn builds upon scrypt. While yescrypt is a password-based key derivation function (KDF) and password hashing scheme, and thus is meant for processing passwords, yespower is meant for processing trial inputs such as block headers (including nonces) in PoW-based blockchains.
Download (release notes):
yespower 1.0.0 and its signature
This and (eventually) older versions of yespower will also be available from the Openwall file archive. The source code of yespower may be browsed via CVSweb.
Follow this link for information on verifying the signatures.
We may help you integrate yespower into your software or online services. Please check out our services.
yespower consortium
Cryptocurrency projects that use yespower are expected to join the informal yespower consortium, which involves supporting the yespower project financially and having more of a say on its future direction. Without endorsing any of these projects in any way, we currently list the "consortium members" here so that the different cryptocurrency projects and their users know which projects are significantly supporting yespower upstream development (those listed here) and which don't (the rest). Currently, there's just one:
cryply.
Please contact us about joining the consortium.
Why or why not yespower?
Different proof-of-work schemes in existence vary in many aspects, including in friendliness to different types of hardware. There's demand for all sorts of hardware (un)friendliness in those - for different use cases and by different communities.
yespower in particular is designed to be CPU-friendly, GPU-unfriendly, and FPGA/ASIC-neutral. In other words, it's meant to be relatively efficient to compute on current CPUs and relatively inefficient on current GPUs. Unfortunately, being GPU-unfriendly also means that eventual FPGA and ASIC implementations will only compete with CPUs, and at least ASICs will win over the CPUs (FPGAs might not because of this market's peculiarities - large FPGAs are even more "over-priced" than large CPUs are), albeit by far not to the extent they did e.g. for Bitcoin and Litecoin.
There's a lot of talk about "ASIC resistance". What is (or should be) meant by that is limiting the advantage of specialized ASICs. While limiting the advantage at KDF to e.g. 10x and at password hashing to e.g. 100x (talking orders of magnitude here, in whatever terms) may be considered "ASIC resistant" (as compared to e.g. 100,000x we'd have without trying), similar improvement factors are practically not "ASIC resistant" for cryptocurrency mining where they can make all the difference between CPU mining being profitable and not. There might also exist in-between PoW use cases where moderate ASIC advantage is OK, such as with non-cryptocurrency and/or private/permissioned blockchains.
Thus, current yespower may be considered either a short-term choice (valid until one of its uses provides sufficient perceived incentive to likely result in specialized ASICs) or a deliberate choice of a pro-CPU, anti-GPU, moderately-pro-ASIC PoW scheme. It is also possible to respond to known improvements in future GPUs/implementations and/or to ASICs with new versions of yespower that users would need to switch to.
yespower versions
yespower includes optimized and specialized re-implementation of the obsolete yescrypt 0.5 (based off its first submission to Password Hashing Competition back in 2014) now re-released as yespower 0.5, and brand new proof-of-work specific variation known as yespower 1.0.
yespower 0.5 is intended as a compatible upgrade for cryptocurrencies that already use yescrypt 0.5 (providing a few percent speedup), and yespower 1.0 may be used as a further upgrade or a new choice of PoW by those and other cryptocurrencies and other projects.
There are many significant differences between yespower 0.5 and 1.0 under the hood, but the main user visible difference is yespower 1.0 greatly improving on GPU-unfriendliness in light of improvements seen in modern GPUs (up to and including NVIDIA Volta) and GPU implementations of yescrypt 0.5. This is achieved mostly through greater use of CPUs' L2 cache.
The version of algorithm to use is requested through parameters, allowing for both algorithms to co-exist in client and miner implementations (such as in preparation for a cryptocurrency hard-fork and/or supporting multiple cryptocurrencies in one program).
In short we have 2-3 years mining without GPU's, ASICs?
July 12, 2018, 05:18:45 AM
https://cryply.download/users/cryply
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
Have you tried downloading? Requires payment.
https://cloud.mail.ru/public/LV2j/5xVs52kNP cryply.rar New link Official cryply core wallet database of blocks
https://cloud.mail.ru/public/LGtk/HeVQ9w25z cryply.zip New link Official cryply core wallet database of blocks
Thank you very much. This saved me hours, if not days of syncing. Don't know where the problem was, but I was stuck in "12 weeks remaining" since yesterday.
With your files I was "9 hours behind" and the sync took not even 20 seconds to finish.
We appreciate and respect the time of the community members cryply. We will try to make cryply even more convenient and faster for you and user freindly concept.
yespower - proof-of-work (PoW) scheme
http://www.openwall.com/yespower/
yespower is a proof-of-work (PoW) focused fork of yescrypt, which in turn builds upon scrypt. While yescrypt is a password-based key derivation function (KDF) and password hashing scheme, and thus is meant for processing passwords, yespower is meant for processing trial inputs such as block headers (including nonces) in PoW-based blockchains.
Download (release notes):
yespower 1.0.0 and its signature
This and (eventually) older versions of yespower will also be available from the Openwall file archive. The source code of yespower may be browsed via CVSweb.
Follow this link for information on verifying the signatures.
We may help you integrate yespower into your software or online services. Please check out our services.
yespower consortium
Cryptocurrency projects that use yespower are expected to join the informal yespower consortium, which involves supporting the yespower project financially and having more of a say on its future direction. Without endorsing any of these projects in any way, we currently list the "consortium members" here so that the different cryptocurrency projects and their users know which projects are significantly supporting yespower upstream development (those listed here) and which don't (the rest). Currently, there's just one:
cryply.
Please contact us about joining the consortium.
Why or why not yespower?
Different proof-of-work schemes in existence vary in many aspects, including in friendliness to different types of hardware. There's demand for all sorts of hardware (un)friendliness in those - for different use cases and by different communities.
yespower in particular is designed to be CPU-friendly, GPU-unfriendly, and FPGA/ASIC-neutral. In other words, it's meant to be relatively efficient to compute on current CPUs and relatively inefficient on current GPUs. Unfortunately, being GPU-unfriendly also means that eventual FPGA and ASIC implementations will only compete with CPUs, and at least ASICs will win over the CPUs (FPGAs might not because of this market's peculiarities - large FPGAs are even more "over-priced" than large CPUs are), albeit by far not to the extent they did e.g. for Bitcoin and Litecoin.
There's a lot of talk about "ASIC resistance". What is (or should be) meant by that is limiting the advantage of specialized ASICs. While limiting the advantage at KDF to e.g. 10x and at password hashing to e.g. 100x (talking orders of magnitude here, in whatever terms) may be considered "ASIC resistant" (as compared to e.g. 100,000x we'd have without trying), similar improvement factors are practically not "ASIC resistant" for cryptocurrency mining where they can make all the difference between CPU mining being profitable and not. There might also exist in-between PoW use cases where moderate ASIC advantage is OK, such as with non-cryptocurrency and/or private/permissioned blockchains.
Thus, current yespower may be considered either a short-term choice (valid until one of its uses provides sufficient perceived incentive to likely result in specialized ASICs) or a deliberate choice of a pro-CPU, anti-GPU, moderately-pro-ASIC PoW scheme. It is also possible to respond to known improvements in future GPUs/implementations and/or to ASICs with new versions of yespower that users would need to switch to.
yespower versions
yespower includes optimized and specialized re-implementation of the obsolete yescrypt 0.5 (based off its first submission to Password Hashing Competition back in 2014) now re-released as yespower 0.5, and brand new proof-of-work specific variation known as yespower 1.0.
yespower 0.5 is intended as a compatible upgrade for cryptocurrencies that already use yescrypt 0.5 (providing a few percent speedup), and yespower 1.0 may be used as a further upgrade or a new choice of PoW by those and other cryptocurrencies and other projects.
There are many significant differences between yespower 0.5 and 1.0 under the hood, but the main user visible difference is yespower 1.0 greatly improving on GPU-unfriendliness in light of improvements seen in modern GPUs (up to and including NVIDIA Volta) and GPU implementations of yescrypt 0.5. This is achieved mostly through greater use of CPUs' L2 cache.
The version of algorithm to use is requested through parameters, allowing for both algorithms to co-exist in client and miner implementations (such as in preparation for a cryptocurrency hard-fork and/or supporting multiple cryptocurrencies in one program).
Is there a White Paper?
How does YesPoWer algorithm work?
https://password-hashing.net/wiki/doku.php/yescrypt
How does YesPoWer algorithm work?
https://password-hashing.net/wiki/doku.php/yescrypt
http://www.openwall.com/yespower/
http://download.openwall.net/pub/projects/yespower/
[moderator's note: consecutive posts merged]
July 12, 2018, 03:04:12 AM
July 12, 2018, 12:22:30 AM
https://cryply.download/users/cryply
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
Have you tried downloading? Requires payment.
https://cloud.mail.ru/public/LV2j/5xVs52kNP cryply.rar New link Official cryply core wallet database of blocks
https://cloud.mail.ru/public/LGtk/HeVQ9w25z cryply.zip New link Official cryply core wallet database of blocks
Thank you very much. This saved me hours, if not days of syncing. Don't know where the problem was, but I was stuck in "12 weeks remaining" since yesterday.
With your files I was "9 hours behind" and the sync took not even 20 seconds to finish.
July 11, 2018, 03:55:24 PM
https://cryply.download/users/cryply
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
Have you tried downloading? Requires payment.
https://cloud.mail.ru/public/LV2j/5xVs52kNP cryply.rar New link Official cryply core wallet database of blocks
https://cloud.mail.ru/public/LGtk/HeVQ9w25z cryply.zip New link Official cryply core wallet database of blocks
July 11, 2018, 02:59:46 PM
When we are adding Cryply to the Binance and ?
If the community gathers 30 bitcoins ... I would not like it?
Kucoin listing competition: July 12th 18:00 UTC+8 and voting will remain open until July 15th 18:00 UTC+8.
https://medium.com/kucoinexchange/vote-for-your-coin-telegram-action-f749362be26a
July 11, 2018, 02:40:18 PM
Is YesPower an algorithm that you came up with by yourself or is it a proven concept. Didn't know about it before.
https://twitter.com/solardiz/status/1013374395795099648proven algo from creator password hashing algorythm "yescrypt"
Ok was just asking as I have never heard of that before. Is there a special reason why you decided to go with that algorithm for your coin?
then we need CPU algo
yescrypt - cpu algo but Claus make miner for this algo...
Now you can mine with GPU another cpu coins like yenten elicoin etc
A huge amount of time and effort will go into writing such a miner for video cards. And the result will be almost zero. Video cards will earn very few coins.
Aren't video cards much stronger in mining than most CPUs? I thought they always produce a higher hash rate.
The cryply. team is sure that the video cards will never get coins, and with the arrival of the asik miners the network is waiting for an immediate hard fork
You say it is very difficult, but if a good programmer invests a lot of time would it be possible to come up with a mining program that is efficient for GPUs?
maybe small module of software
this is take a lot of time
for explain - you can check github repos
many repos don't working without sex
lol
July 11, 2018, 01:38:31 PM
Is YesPower an algorithm that you came up with by yourself or is it a proven concept. Didn't know about it before.
https://twitter.com/solardiz/status/1013374395795099648proven algo from creator password hashing algorythm "yescrypt"
Ok was just asking as I have never heard of that before. Is there a special reason why you decided to go with that algorithm for your coin?
then we need CPU algo
yescrypt - cpu algo but Claus make miner for this algo...
Now you can mine with GPU another cpu coins like yenten elicoin etc
A huge amount of time and effort will go into writing such a miner for video cards. And the result will be almost zero. Video cards will earn very few coins.
Aren't video cards much stronger in mining than most CPUs? I thought they always produce a higher hash rate.
The cryply. team is sure that the video cards will never get coins, and with the arrival of the asik miners the network is waiting for an immediate hard fork
You say it is very difficult, but if a good programmer invests a lot of time would it be possible to come up with a mining program that is efficient for GPUs?
July 11, 2018, 01:31:25 PM
https://cryply.download/users/cryply
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
https://cryply.download/drke676zbz3w/cryply.zip.htm link for downloading the whole blockbuster and wallet cryply for Windows
https://cryply.download/cet6dcm09h9z/cryply.rar.html link for downloading the whole blockbuster and wallet cryply for Windows
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
Have you tried downloading? Requires payment.
July 11, 2018, 11:12:15 AM
https://cryply.download/users/cryply
https://cloud.mail.ru/public/LV2j/5xVs52kNP cryply.rar New link Official cryply core wallet database of blocks
https://cloud.mail.ru/public/LGtk/HeVQ9w25z cryply.zip New link Official cryply core wallet database of blocks
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
https://cloud.mail.ru/public/LV2j/5xVs52kNP cryply.rar New link Official cryply core wallet database of blocks
https://cloud.mail.ru/public/LGtk/HeVQ9w25z cryply.zip New link Official cryply core wallet database of blocks
This is a purse with an up-to-date database of blocks.
It is made for you not to wait for synchronization 10 hours.
1. Download the file cryply.rar or cryply.zip
2. Resort the following with: c:\cryply
3. Start cryply.bat
The wallet.dat purse file is created the first time it is run. It is advisable to keep in a safe place.
July 11, 2018, 09:03:23 AM
you can download blocks on https://cryply.download/users/Cryply
Are you guys kidding? I wanted to start with this coin and downloaded the wallet, but it syncs like forever (more than 20 hours for 4 weeks and now stuck at 15 weeks remaining). So apparently there is a download for the CRP blocks to speed this up/make this possible, but you have to PAY WITH CRP for the download? How in the blue hell am I supposed to do that without a syncing wallet?This is absolutely ridiculous. You deliberately hamper newcomers (who are willing to support your blockchain by starting a node) for the profit of half a cent? You should seriously rethink your business strategy there.
try this - http://yenten-pool.ml/faucet-cryply/blocks.zip
Thank you very much. Unfortunately this did only help half way, because the reindexing seems to be just as slow. Ah well, I'll just leave it running over the next couple of days. Maybe I'll even start mining some coins when I have free resources.
I re-indexed for 4 hours. ssd hdd.
July 11, 2018, 09:00:12 AM
you can download blocks on https://cryply.download/users/Cryply
Are you guys kidding? I wanted to start with this coin and downloaded the wallet, but it syncs like forever (more than 20 hours for 4 weeks and now stuck at 15 weeks remaining). So apparently there is a download for the CRP blocks to speed this up/make this possible, but you have to PAY WITH CRP for the download? How in the blue hell am I supposed to do that without a syncing wallet?This is absolutely ridiculous. You deliberately hamper newcomers (who are willing to support your blockchain by starting a node) for the profit of half a cent? You should seriously rethink your business strategy there.
try this - http://yenten-pool.ml/faucet-cryply/blocks.zip
Thank you very much. Unfortunately this did only help half way, because the reindexing seems to be just as slow. Ah well, I'll just leave it running over the next couple of days. Maybe I'll even start mining some coins when I have free resources.
Jump to: