Bitcoin Forum

PROJECT

OrmNetwork its a completely decentralized network without using an explorer. The project provides profitability when using mining on both video cards and processors. OrmNetwork use new algo - Blake3P (P-Privacy). The development of smart contracts based on our project is already underway, the release is expected at the end of September this year.

We have slightly improved the old algorithm and added new functions. One of the functions of decentralization and privacy is working through a secure block explorer. Block explorer allows you to view block height statistics, but does not provide transaction tracking.

Currently, we are developing a block explorer and decentralized smart contracts based on project OrmNetwork.

GITHUB
https://github.com/OrmNetwork/ORMCore/releases/tag/v1.2.2

WEBSITE
https://ormnetwork.org

BLOCK EXPLORER
Decentralized version in development (like Monero)

TWITTER
https://x.com/OrmNetwork

DISCORD
https://discord.gg/jrfHtcaK

EXCHANGES
Coming soon

wallet doesnt work, need more info on connecting to node and mining!

After launching the wallet, wait until the blocks are completely synchronized and only then start creating the wallet itself

i have the daemon syncing and wallet, but what about a miner?

The miner had a connection problem, we are currently working on a patch for the wallet. As soon as we make a patch, we will include the miner itself with corrections. Sorry for the problematic start, the nodes can’t cope with the flow. Thank you for your patience

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?

no premine, but the project started before the announcement here, we have several miners. Current block - 2150

No premine, but someone already mining with no miner available for the community... Not fair

agreed, the miner should be released atleast and if it doesnt work then so be it but atleast make it available!

the load increased - a decision was made to patch both the wallet and the miner. We are working on it, the height of the block has increased quite a bit. Few hours and we release new version wallets with miner.

This is called premine.

Someone is actually mining!

go install . ./cmd/...

builds the following binaries:

genkeypair
kaspactl
kaspad
kaspaminer
kaspawallet

Such installation process is confusing for those who have Kaspa (the implementation in Go) preinstalled
as Kaspas binaries get overwritten. Would you consider renaming them in your building instructions?
I am writing about it here as you have no issues in your Github repo.

Don't worry .
these guys are now mining on an old miner and they will make you a new miner)

there are enough coins for everyone))

Check out github releases: https://github.com/OrmNetwork/ORMCore/releases/tag/v1.2.2
New wallets with path and miner
Add miner for start mining for all

file ormcore-v1.2.2-linux64.tar.gz :

ormcore-v1.2.2-linux64.tar.gz: RAR archive data, v5


The release is not a gzip file, but a rar file.

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

We should also have some extra info about how to mine and have the opportunity to chat in the discord group!

sorry, forgot about linux.
Few minutes and add miner

Check now and rerun linux wallets/miner

ormcore-v1.2.2-linux64.tar.gz is not RAR archive
No files to extract

Done
Check now.
Sorry for mistake

The node is synced , but the wallet doesn t work and getting error on windows

You really need to open a channel in discord so we can all communicate these problems together.  would be alot more simple.

the wallet is available for use after synchronization. Wait for the blocks to fully synchronize

We will open the server within the next day. This is done to prevent spam due to problems that we ourselves are aware of and are fixing. Thank you for patience.

ok just completing sync, should be mining in a moment all going well!

2024-07-29 05:44:40.312 [INF] PROT: Received 60786 UTXO set chunks so far, totaling in 60786000 UTXOs
2024-07-29 05:44:40.977 [INF] PROT: Received 60885 UTXO set chunks so far, totaling in 60885000 UTXOs
2024-07-29 05:44:41.616 [INF] PROT: Received 60984 UTXO set chunks so far, totaling in 60984000 UTXOs
2024-07-29 05:44:41.934 [INF] PROT: Finished receiving the UTXO set. Total UTXOs: 61019837
2024-07-29 05:44:41.934 [INF] BDAG: Checking that the given pruning point is the expected pruning point
2024-07-29 05:44:44.567 [INF] BDAG: Updating consensus state manager according to the new pruning point 797a5ec191b77e40fb4fdb169380f4081f44bca3be7b28607263893abc33f295



The data packets simply cannot be synchronized


The data packets simply cannot be synchronized

When opening wallet it simply closes my firefox and google chrome then does nothing.. Unsure what the point of that is.

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

2024-07-29 00:09:26.165 [INF] PROT: Received 60687 UTXO set chunks so far, totaling in 60687000 UTXOs
2024-07-29 00:09:27.264 [INF] PROT: Received 60786 UTXO set chunks so far, totaling in 60786000 UTXOs
2024-07-29 00:09:28.254 [INF] PROT: Received 60885 UTXO set chunks so far, totaling in 60885000 UTXOs
2024-07-29 00:09:29.227 [INF] PROT: Received 60984 UTXO set chunks so far, totaling in 60984000 UTXOs
2024-07-29 00:09:29.813 [INF] PROT: Finished receiving the UTXO set. Total UTXOs: 61019837
2024-07-29 00:09:29.813 [INF] BDAG: Checking that the given pruning point is the expected pruning point
2024-07-29 00:09:53.151 [INF] BDAG: Updating consensus state manager according to the new pruning point 797a5ec191b77e40fb4fdb169380f4081f44bca3be7b28607263893abc33f295

same here

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!!!!!!!!!!!  >:( >:( >:( >:( >:( >:(

has anyone manage to get the wallet to open? mine just closes my internet browsers

also why tf no discord chat rooms this is dumb having to talk and wait in a forum

Is there any big guy who can look at the program? His wallet is different from others. Is there any virus in it?

just make sure to open it on a VM with nothing else on the machine, gives u a layer of security, should be fine

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

we need an updated full data2 folder