Search content
Sort by
Showing 20 of 567 results by LTCMAXMYR
Re: [ANN] [PASC] PascalCoin: Deletable blockchain - Like Bank accounts [SAFEBOX]
I have encountered the same problem and lost more than 300,000 PASC
Hi all !
There is a problem with the balance on the wallet, or rather, the balance has disappeared and I cannot restore it. Background:
1. This coin was mined about a year ago. The wallet was version 5.3 - 2020-03-12 (PascalCoinWalletB5.3.3.0_64b.exe). If you launch it now, there is a balance!
2. If you install the version (any of the above) - synchronization goes through, everything is ok, but - there is no balance, and most importantly - he does not see the wallet! The address is simply absent, and any actions such as importing a private key or slipping a backup copy of a wallet do not change anything!
Actually the question is - what is it and how to fix it?
UPD And that's not all ... A few hours later, I looked into my wallet ... And again there is nothing !!!! There is no wallet number or balance. There are 28 messages about protocol change ... What's going on? Is this how it should be?
There is a problem with the balance on the wallet, or rather, the balance has disappeared and I cannot restore it. Background:
1. This coin was mined about a year ago. The wallet was version 5.3 - 2020-03-12 (PascalCoinWalletB5.3.3.0_64b.exe). If you launch it now, there is a balance!
2. If you install the version (any of the above) - synchronization goes through, everything is ok, but - there is no balance, and most importantly - he does not see the wallet! The address is simply absent, and any actions such as importing a private key or slipping a backup copy of a wallet do not change anything!
Actually the question is - what is it and how to fix it?
UPD And that's not all ... A few hours later, I looked into my wallet ... And again there is nothing !!!! There is no wallet number or balance. There are 28 messages about protocol change ... What's going on? Is this how it should be?
Re: [ANN] DERO: DAG + Cryptonote + Bulletproofs + SSL + POW + Smart Contracts
Beware of the kucoin exchange, the DERO you deposited may not belong to your account, especially large transfers.
I have spent 4 days to communicate with the customer service, and was asked to provide a 30USDT processing fee.
No progress has been made, and the customer service is quite unprofessional.
I have spent 4 days to communicate with the customer service, and was asked to provide a 30USDT processing fee.
No progress has been made, and the customer service is quite unprofessional.
Re: [ANN] [PASC] PascalCoin: Deletable blockchain - Like Bank accounts [SAFEBOX]
TestNet Bug report,
PascalCoinWallet_TESTNET_5.Beta.1_Windows and PascalCoinWallet_TESTNET_5.Beta.2_Windows have the same problem.
Miner sometimes doesn't work , debug，then found RPC info "part1" length is 89 bytes, the general case is 90 bytes.
both wallet and miner are running on WIN7 X64.
PascalCoinWallet_TESTNET_5.Beta.1_Windows and PascalCoinWallet_TESTNET_5.Beta.2_Windows have the same problem.
Miner sometimes doesn't work , debug，then found RPC info "part1" length is 89 bytes, the general case is 90 bytes.
both wallet and miner are running on WIN7 X64.
Re: [ANN] [PASC] PascalCoin: Deletable blockchain - Like Bank accounts [SAFEBOX]
I revisited the URandomHash2 code, the problem with the nonce scan still exists, and I found a new flaw.
Too small memory requirements will make FPGAs easier to implement.
Suggest:
1. Do not use final round in the middle state, miner must calculate the full round
2. Increase the M size so that the final memory requirement reaches 2MB or more.
Too small memory requirements will make FPGAs easier to implement.
Suggest:
1. Do not use final round in the middle state, miner must calculate the full round
2. Increase the M size so that the final memory requirement reaches 2MB or more.
Re: [ANN] [PASC] PascalCoin: Deletable blockchain - Like Bank accounts [SAFEBOX]
a bug in RandomHash2.
URandomHash2.pas
line 267
LParentOutputs := Hash(ABlockHeader, ARound - 1, AFoundLastRound);
if AFoundLastRound > 0 then
// Previous round was the final round, so just return it's value
Exit(LParentOutputs); //bug is here
There are 1/4 chances in round 2, returning results,without continue calculating the data behind,
Discarding some nones will result in hundreds of performance gains
URandomHash2.pas
line 267
LParentOutputs := Hash(ABlockHeader, ARound - 1, AFoundLastRound);
if AFoundLastRound > 0 then
// Previous round was the final round, so just return it's value
Exit(LParentOutputs); //bug is here
There are 1/4 chances in round 2, returning results,without continue calculating the data behind,
Discarding some nones will result in hundreds of performance gains
now you will see the asic miners on https://bsod.pw/site/miners xvg lyra2v2
Miners Version (xvglyra)
Version Count Donators ES Percent Hashrate* Avg
cgminer/4.11.1 9 - - 108.24% 37 GH/s 4.1 GH/s
CryptoDredge/0.9.1 2 - 2 0.21% 70.2 MH/s 35.1 MH/s
Total 11 0 2 34.1 GH/s 3.1 GH/s
Miners Version (xvglyra)
Version Count Donators ES Percent Hashrate* Avg
cgminer/4.11.1 9 - - 108.24% 37 GH/s 4.1 GH/s
CryptoDredge/0.9.1 2 - 2 0.21% 70.2 MH/s 35.1 MH/s
Total 11 0 2 34.1 GH/s 3.1 GH/s
Re: Vertcoin [VTC][ANN] Segwit Activated | ASIC Resistant Decentralized GPU Mining
lyra2v2 ASIC is coming,when change algo?
https://www.akminer.com/all-products/the-worlds-first-the-most-power-efficient-28nm-lyra2rev2-asic-miner-dayun-zig-z1
https://www.akminer.com/all-products/the-worlds-first-the-most-power-efficient-28nm-lyra2rev2-asic-miner-dayun-zig-z1
next lyra2z ASIC?
XZC fork is coming ,the lyra2Z ASIC is uselessIf you think the boards will lose their value then don't buy them. I definitely remember you from discord. FUD.
A new risk, if the chip is locked by KEY, then the board is worthless unless you know the key, it have no second-hand value like GPU
The key doesn't prevent unencrypted designs from running. Keep in mind, if we didn't do this it would also open an attack vector where a developer could maliciously burn the efuse preventing any designs from operating but their own.
I'm pretty sure you were already told this on discord?
So if you reviewed the documentation you would know that the chip can still load unencrypted bitstreams (assuming you use the correct options).
Once the key is loaded, yes, the key cannot be changed.
The ram key is wiped when the board loses power. The board doesn't have a battery.
1.when board begin to run ,it gen a random number,and append your secretive key1,then SHA2(or others algo) it
2.software read the hash message,send to a server,(the miner is online,so it is easy to connect the server)
3.the server append the hash with your secretive key2,then SHA2(or others algo) it ,send back
4.the board check the result,if match ,run miner,otherwise ,do nothing.
so ,you just need two key,
every new developer or new algo can have his own key,
also the boards will not lose their value.
A new risk, if the chip is locked by KEY, then the board is worthless unless you know the key, it have no second-hand value like GPU
The key doesn't prevent unencrypted designs from running. Keep in mind, if we didn't do this it would also open an attack vector where a developer could maliciously burn the efuse preventing any designs from operating but their own.
I'm pretty sure you were already told this on discord?
CAUTION! If this bit is programmed to 1, the device cannot be
used unless the AES key is known. Return material
authorization (RMA) returns cannot be accepted and the
Vivado Indirect SPI/BPI flash programming flow cannot be
used if this bit is programmed. You must have external
configuration memories programmed BEFORE you blow this
fuse if you intend to use Vivado for this programming.
why not use the RAM to store the key?