 Show Posts
|
|
Pages: [1]
|
More than three months since the launch and while the team advertizes SPECTRE to be a privacy coin, this is just a fork of KASPA,
without any privacy features implemented that would differentiate it from KAS. I am so disappointed.
excellent, be disappointed while the rest of us fill up! |
|
|
|
It looks like they just compiled a kaspad executable, changed the file name, and left everything else the same. Windows Wallet doesn’t work, and it’s still not fixed after two versions. It looks like it was designed to inject a trojan. But again, the trojan failed because of lack of skills.Discord also does not allow everyone to communicate.This behavior is hard to understand.
yes ive closed my node and removed everything. IDK if ill intent is at play but this ISNT how you start off a project. This is a straight clone of KASPA/KASPAD with what seems like the original version of HARBIMINER but with less work to even change the executables. not gonna play this game until there is real progress and clear lines of communication in discord so the whole community can figure this out. Really disappointed! |
|
|
|
|
on linux using the cli wallet
./ormcorewallet create i think was the command
|
|
|
|
|
im about done with this already! node is synced, no issues, have address on linux, no issues, wallet i synced no issues, have miners pointed to node, no issues, STILL NO BLOCKS! Lines of communcation = PROBLEM!
Updated to the latest wallet. makes no difference to mining.
|
|
|
|
|
an update for what, sorry to keep going on but were wasting power here trying to mine brocks that cannot be mined. nearly 2 hours and not a single block isnt right. discord needs to be opened asap, this isnt a real means of communication while trying to get the project going. sorry to be a nag but if im losing patience i guess there are others. all the time someone is still mining valid blocks i presume but we have no way to verify anything.
|
|
|
|
we working on fixes
are we sure here that were actually mining this chain, something doesnt add up. |
|
|
|
|
dont think something is quite right, has anyone actually found and been paid a block yet. I have significant hash on this for about 1hr and no blocks!
|
|
|
|
|
we need an updated full data2 folder
|
|
|
|
|
719 [INF] BDAG: Done applying the pruning point proof
2024-07-28 22:55:03.719 [INF] PROT: Downloading the past pruning points and the pruning point anticone from <d73e75a2b284e2385aa83a6b4ec5e956: 87.121.72.51:16111>
2024-07-28 22:55:03.719 [INF] PROT: IBD with pruning proof from <d73e75a2b284e2385aa83a6b4ec5e956: 87.121.72.51:16111> was unsuccessful. Deleting the staging consensus. (the proposed pruning point is the same as the current pruning point)
2024-07-28 22:55:03.719 [INF] PRFX: Deleting database prefix &{0}
2024-07-28 22:55:04.575 [INF] PRFX: Compacting database after prefix delete
2024-07-28 22:55:05.356 [INF] PROT: IBD with peer <d73e75a2b284e2385aa83a6b4ec5e956: 87.121.72.51:16111> finished (interrupted: the proposed pruning point is the same as the current pruning point)
2024-07-28 22:55:05.356 [ERR] PROT: Non-critical peer protocol error from HandleIBD, printing the full stack for debug purposes:
====================================================
the proposed pruning point is the same as the current pruning point
====================================================
2024-07-28 22:55:05.356 [INF] PROT: Disconnecting from <d73e75a2b284e2385aa83a6b4ec5e956: 87.121.72.51:16111> (reason: the proposed pruning point is the same as the current pruning point)
2024-07-28 22:55:05.692 [INF] PROT: IBD started with peer <5223658fe469452e921fc51f06da1a2b: 75.119.146.150:16111>
2024-07-28 22:55:05.692 [INF] PROT: IBD started with peer <5223658fe469452e921fc51f06da1a2b: 75.119.146.150:16111> and relayBlockHash 5ead142a42a22083aebe314e81129a722400401edeefc39fcf6de24aa8407275
2024-07-28 22:55:05.692 [INF] PROT: Syncing blocks up to 5ead142a42a22083aebe314e81129a722400401edeefc39fcf6de24aa8407275
2024-07-28 22:55:05.692 [INF] PROT: Trying to find highest known syncer chain block from peer <5223658fe469452e921fc51f06da1a2b: 75.119.146.150:16111> with relay hash 5ead142a42a22083aebe314e81129a722400401edeefc39fcf6de24aa8407275
2024-07-28 22:55:05.850 [INF] PROT: Found highest known syncer chain block 89ef90903bd7e882f6fcce02aab9975c566860fa31384465e5ed6200f7307b7c from peer <5223658fe469452e921fc51f06da1a2b: 75.119.146.150:16111>
2024-07-28 22:55:05.850 [INF] PROT: Starting IBD with headers proof
2024-07-28 22:55:05.933 [INF] PROT: Downloading the pruning point proof from <5223658fe469452e921fc51f06da1a2b: 75.11
stuck in a loop now! This is a bust atm
|
|
|
|
|
just make sure to open it on a VM with nothing else on the machine, gives u a layer of security, should be fine
|
|
|
|
after about 10 mins it will start to try and find peers or somethings, but still no accepted blocks also for a new chain why so many UTXOS? update 2024-07-28 22:29:13.420 [INF] UTIN: Starting UTXO index reset FFS! kaspad shutdown!!!!!!!!!!!  |
|
|
|
|
2024-07-28 22:13:03.033 [INF] PROT: Received 60786 UTXO set chunks so far, totaling in 60786000 UTXOs
2024-07-28 22:13:03.904 [INF] PROT: Received 60885 UTXO set chunks so far, totaling in 60885000 UTXOs
2024-07-28 22:13:04.687 [INF] PROT: Received 60984 UTXO set chunks so far, totaling in 60984000 UTXOs
2024-07-28 22:13:05.051 [INF] PROT: Finished receiving the UTXO set. Total UTXOs: 61019837
2024-07-28 22:13:05.051 [INF] BDAG: Checking that the given pruning point is the expected pruning point
2024-07-28 22:13:20.037 [INF] BDAG: Updating consensus state manager according to the new pruning point 797a5ec191b77e40fb4fdb169380f4081f44bca3be7b28607263893abc33f295
same for me same point
|
|
|
|
|
ok just completing sync, should be mining in a moment all going well!
|
|
|
|
|
You really need to open a channel in discord so we can all communicate these problems together. would be alot more simple.
|
|
|
|
|
ormcore-v1.2.2-linux64.tar.gz is not RAR archive
No files to extract
|
|
|
|
|
still only ormcored and ormcorewallet, no miner!
Creating ormcore-v1.2.2-linux64 OK
Creating ormcore-v1.2.2-linux64/bin OK
Extracting ormcore-v1.2.2-linux64/bin/ormcored OK
Extracting ormcore-v1.2.2-linux64/bin/ormcorewallet OK
|
|
|
|
|
agreed, the miner should be released atleast and if it doesnt work then so be it but atleast make it available!
|
|
|
|
|
Ok maybe is best to communicate this in your discord that it isnt ready. are blocks being mined then or chain halted if a problem with the miner. is this being premined then?
|
|
|
|
|
i have the daemon syncing and wallet, but what about a miner?
|
|
|
|
|
wallet doesnt work, need more info on connecting to node and mining!
|
|
|
|
|
