Bitcoin Forum

Quick links:
PHANTOM GhostDAG: https://eprint.iacr.org/2018/104.pdf
Github: https://github.com/kaspanet/kaspad/
Block Explorer: https://explorer.kaspa.org/
KDX Wallet: https://kdx.app
Discord: https://discord.gg/SfHCaDchrs
Chinese guide: https://mp.weixin.qq.com/s/KFwyfnRv5glxXuhaDHlJMQ
Russian guide: https://2ch.hk/cc/res/753039.html#753562

Currently mining is not the mainnet, you need to write clearly. . waste time.

currently (26th November 2021) network has moved OUT of Testnet and is in a progression stage that the devs have called GAMENET.

mined coins ARE valid, but will be subject to cosmetic changes as to how your KAS are viewed in your wallet.
Current block rewards are 500 (KAS)

so these will be valid coins in Mainnet, but may show slightly differently in your wallet, dependent on final decided monetary policies.

I took a quick look, very very intersting mechanism of rewarding, not another ASIC resistance coin, but it has some sophisticated mechanism against whale miners... I'll subscribe to this topic, cuz of my heavy work load, will check again in few weeks.

Hey yeah even weak cpu can get some reward daily and that is what make that coin good and worldwide. In my opinion one of best I meet in crypto space. Waiting for updates and where it will go :)

hi.

GUI wallet needed because this procedure is hard for non programmers like me..

But anyway; good endeavor  ;)

---

i have tried all my possible with the tutorial, i made appdata directory writable but i got only one folder which is kaspad-mainnet and not the three mentioned in the tutorial for windows...

i would like to mine and contribute to this project, but unfortunately i am not a programmer, how can you make things easier ?

---

sorry i am syncing but the three folder described in the guideline are not created

[moderator's note: consecutive posts merged]

You make appdata folder ???

Mate google where it is located cose each windows by default have appdata folder

look in settings for folder options go to tab called view and mark show hidden files and folders

then your appdata folder will be located in C:/Users/Yourusername

Inside that correct appdata folder you will see folder called Local and inside that folder you will see Kaspad folder.

If you dont know how to see hidden files and folders google it and full correct path is :

C:/users/yourusername/appdata/local/kaspad

Is this project standalone or a fork from another project?
Who is behind the development?
What is the mining algorithm?

Standalone, created from scratch
The academics who designed the architecture are listed in the technical paper (although not development team - who seem to be a few anons in discord)
algo is a variation of heavyhash

What is the total amount after the mainnet launch?

The monetary policy is being drawn up. Expect full details within a couple of weeks.

Very INteresting . . started some hash on it yesterday . .

Wen u see literal geniuses coming up with some BRAND NEW shit, its best to pay attention AND spec-mine the shit out of it!!!


https://eprint.iacr.org/2018/104.pdf

[2021-11-26T20:34:54Z INFO  kaspa_miner::miner] launching: 128 miners
[2021-11-26T20:34:54Z INFO  kaspa_miner::client] Kaspad version: 0.11.6
Error: "Could not decode address: decoded address is of unknown format: string not all lowercase or all uppercase"

make sure you include the part before the actual address

---

Quick and easy guide to CPU solo mine Kaspa on a linux-based computer.

Firstly, let's do some housework, in prep for the screens you will need. In this guide we will use both pm2 and screen -dmS commands.









let it synchronise (shouldn't take too long at this point) you can watch it run by typing the command;


and Cntrl-C to close the pm2 (it will continue in the background)

When the node is fully synchronised you will see BLOCK ACCEPTED outputs.

Get the miner:


make the miner executable


run the miner in screen -dmS


*NOTE* the above is MY address, if you mine to it, I thank you for your donation. Please amend the string with your own KASPA address.


You can have a look in on the processes by;

1. look in on the node - to make sure it's synchronised and working OK:


1a. and close it using Cntrl-C

2. look in on your miner - to see if it is finding blocks:


2a. and detach the screen using Cntrl-A, then pressing (the letter on your keyboard) d.

What exactly is your aim for this project. We have thousands of alts already, what niche do you expect to excel? It is hard to gain loyal supporters because there are much solid projects out there. What do you think will give you edge to attract the interest of some users?

the aims are all written in the OP.  Thus is such the purpose of an ANN. I suggest you take time to read the technical paper, to familiarise yourself with the architecture.

This project has been in development for a long time; the total amount has not been worked out, indicating that there is no long-term plan. . . Do whatever you want

Yeah, i agree to a point and merely wanted to make sure that EVERYONE gets a fair and equal start on Kaspa. I will monitor and update this thread accordingly.
Holding back from making announcements or keeping info back - like the telegram bot which gives network hashrate, didn't sit right with me and the coin is no longer restricted to a few people on discord.

decentralise.

For anyone interested, I wrote two blog posts about part of the things that Kaspa is trying to fix and how:

https://someone235.medium.com/how-increasing-the-throughput-harms-bitcoins-security-76ed62313227
https://someone235.medium.com/scaling-bitcoin-with-blockdag-d785174a3402

Their discord server is very active. If you want to get a quick answer, you need to join their discord server link

---

The computing power of the whole network has exceeded 12G/s, incredible!
It's only a few days

[moderator's note: consecutive posts merged]

Need more CPU miners, come on over and get in on this coin!

kaspa-miner.exe -t 10 --mining-address kaspa: qrug9kefug0tj62k789kv067dw8fh6e50f0vsacmuwnznxz9ratc62hxlzr46

how do i configure ??? ???

kaspa-miner.exe -t 10 --mining-address kaspa:qrug9kefug0tj62k789kv067dw8fh6e50f0vsacmuwnznxz9ratc62hxlzr46

Get rid of the space between kaspa: and the rest of the address

Kaspa's discord server is quite active. If you ask mining related questions or tutorials there, you will get a reply faster!

Download the miner from here -  https://github.com/elichai/kaspa-miner/releases
Here's an example of a bat file:

The network has just started and the size of the folder with blocks is already 2.64 GB.
This is a lot.
Will there be any work to optimize the size of stored blocks?

They have a concept in place, it will be explained here shortly

https://eprint.iacr.org/2021/623.pdf

Hi, I am from the Kaspa research team.

All and all we store three components: full header data above the pruning block, the UTXO set of the pruning block, and a proof of correctness for the UTXO set.

We have a fancy pruning mechanism (cf. https://research.kas.pa/t/some-of-the-intuition-behind-the-design-of-the-invalidation-rules-for-pruning/95) that allows us to remove old block data. At full capacity the size of a block payload is bound by 100kB and the size of a block header is bound by (100 +32*log_2(past size))B. In the distant future where we have a trillion blocks in the network (this will take about 30 thousand years of one block per second) we will have that log_2(past size) = 40, so let us assume that log_2(past size) <= 40. This means that the header size is bound by (100+32*40)B which is just below 1.5kB. For simplicity assume for now that he entire block size is 100kB. We store three days worth of full block data which, at a rate of one block/second, accumulates to about 26GB (note that this bound assumes that all blocks are at maximum capacity, no assumptions on average number of txns per block).

The UTXO correctness proof (cf. https://github.com/kaspanet/research/issues/3) requires that we keep additional log_2(number of blocks in the network) headers (not full blocks). Using again the assumption log_2(past size) <= 40  this adds about 60kB of data, which is completely negligible. Currently we store all block headers, as it requires some care to remove them without accidentally removing headers required for the proof and our dev team hasn't got around to this yet, this is a completely technical issue which will be resolved in the near future. (There is another detail I swept under the rug, which is that we also have to store the headers of all pruning blocks. This means one header per day. While this technically grows at a rate O(n*logn) the constant is ridiculously small: it is bound by 1.5kB/day, which are about 570kB a year).

The only thing that grows linearly is the pruning block UTXO set itself. It currently requires a field of a fixed size for every unspent output in the network. It is hard to predict how fast this set grows as this heavily depends on user behavior. We will resolve this in the future by means of cryptographic accumulators (cf. https://en.wikipedia.org/wiki/Accumulator_(cryptography)). An accumulator is a way to represent a large set succinctly such that it is impossible to recover the set itself (due to information theoretic compression bounds), but it is possible to verify that an element is in the set given a proof. This means that every user will only need to store the (proofs of) their own unspent outputs, and the nodes will only have to verify this proof against the accumulator, which is much smaller than the actual number of unspent outputs. The sizes of the accumulator and the proofs depends on the exact solution we will choose.

---

I feel that I should clarify: the bot in question was written by a community member which is not a member of the core team and who does not want to share their code, and I am sure they have their reasons. This has nothing to do with Kaspa. All the bot does is to issue a couple of commands to our (completely open source and publicly available) node and print the result to a Telegram channel. Seems a bit unfair to me to conclude from this that the core team is holding back on anything.

We strongly believe in openness, which is why we made the network publicly available and invited the community to get involved as soon as possible, and in particular, without any premining whatsoever.

The reason we wanted to delay the announcement is because we wanted the coin to be more well tested, and the ecosphere more well developed, before using our one chance to garner attention off the BCT board. But since this is a community coin, we can't (and don't want to) prevent anyone from making announcements. Anyway, now that the cat is out of the bag feel free to ask me anything.

It is announced on the discord server that the accurate monetary policy will be released soon. I hope to release it soon. I have been looking forward to this policy for nearly a week!

Thanks for the detailed answer.
I have more questions: is there a GUI wallet planned?
and how much total supply?

Hey Deshe, you beast me to it with your own answer ;)

Thxx!

Wolfie

That's crazy!
Why does the computing power of the whole network suddenly rise so much?
I'm only 24M/s, and now I can only dig 30000 kaspa a day

What is going on with this coin

when i launch ./kaspad i get this

2021-12-02 11:51:35.711 [INF] KASD: Version 0.11.6
2021-12-02 11:51:35.712 [INF] KASD: Loading database from '/home/miner2/.kaspad/kaspa-mainnet/datadir2'
2021-12-02 11:51:35.966 [INF] ADXR: Loaded 3067 addresses and 0 banned addresses
2021-12-02 11:51:35.967 [INF] TXMP: P2P Server listening on [::]:16111
2021-12-02 11:51:35.967 [INF] TXMP: RPC Server listening on [::]:16110
2021-12-02 11:51:35.967 [INF] CMGR: Connecting to [2600:1700:d78:1cf0::46]:16111
2021-12-02 11:51:36.968 [INF] CMGR: Connecting to 65.108.46.85:16111
2021-12-02 11:51:37.060 [INF] TXMP: P2P Connected to 65.108.46.85:16111
2021-12-02 11:51:37.060 [INF] CMGR: Connecting to [2001:14ba:3fe:9600:500d:cd4a:b440:5453]:16111
2021-12-02 11:51:37.252 [INF] PROT: IBD started
2021-12-02 11:51:37.304 [INF] PROT: Downloading headers from <39b2560a869fc42bddeff257167b09cb: 65.108.46.85:16111>
2021-12-02 11:51:38.061 [INF] CMGR: Connecting to [240e:3b5:34e0:f191:8e63:f401:cd10:62cd]:16111
2021-12-02 11:51:39.061 [INF] CMGR: Connecting to [2409:8a30:22f:e180:24c3:4fe7:1b6b:2d8a]:16111
2021-12-02 11:51:40.062 [INF] CMGR: Connecting to 140.250.146.11:16111
2021-12-02 11:51:40.458 [INF] TXMP: P2P Connected to 140.250.146.11:16111
2021-12-02 11:51:40.458 [INF] CMGR: Connecting to [2a01:4f9:6b:431d::2]:16111
2021-12-02 11:51:41.459 [INF] CMGR: Connecting to [2a10:800e:218d:0:c06:5a86:6163:4d71]:16111
2021-12-02 11:51:49.743 [INF] BDAG: Processed 1 block and 315 header in the last 13.78s (1 transaction, 2021-12-02 11:46:31.638 +0000 GMT)
2021-12-02 11:51:50.338 [INF] BDAG: Resolving virtual. This may take some time...
2021-12-02 11:51:50.682 [INF] BDAG: Resolved virtual
2021-12-02 11:51:50.682 [INF] PROT: IBD finished successfully
2021-12-02 11:51:51.294 [INF] PROT: IBD started
2021-12-02 11:51:51.340 [INF] PROT: Downloading headers from <39b2560a869fc42bddeff257167b09cb: 65.108.46.85:16111>
2021-12-02 11:51:51.899 [INF] BDAG: Resolving virtual. This may take some time...
2021-12-02 11:51:51.921 [INF] BDAG: Resolved virtual
2021-12-02 11:51:51.921 [INF] PROT: IBD finished successfully
2021-12-02 11:51:52.194 [INF] PROT: Accepted block d29174246d50f8d6b1393f318aa7f075e274971ac49806e96a31a4b407eccfcd via relay
2021-12-02 11:51:53.740 [INF] PROT: Received a block with missing parents, adding to orphan pool: 2e46a2594395d705b7b8ee8883472b33e43aa726e91ee1799de669f4e0958cf0
2021-12-02 11:51:53.740 [INF] PROT: Block 2e46a2594395d705b7b8ee8883472b33e43aa726e91ee1799de669f4e0958cf0 has 1 missing ancestors. Adding them to the invs queue...
2021-12-02 11:51:53.829 [INF] PROT: Accepted block 495eef8d6f6f6a773b5fb2f9d1fe2742c77175d809da3d8ccfa481f08912bd6c via relay
2021-12-02 11:51:53.861 [INF] PROT: Unorphaned block 2e46a2594395d705b7b8ee8883472b33e43aa726e91ee1799de669f4e0958cf0
2021-12-02 11:51:54.118 [INF] PROT: Accepted block b6d5bd6032e664a28ec509863f79faa0fb42b083baddf1e90ad94d4ddd7f7806 via relay
2021-12-02 11:51:54.374 [INF] PROT: Received a block with missing parents, adding to orphan pool: 428eea9316bdbbe31a58a8b47aeece0a89c715e1c0754ec74a50fe5b93058d65
2021-12-02 11:51:54.374 [INF] PROT: Block 428eea9316bdbbe31a58a8b47aeece0a89c715e1c0754ec74a50fe5b93058d65 has 1 missing ancestors. Adding them to the invs queue...
2021-12-02 11:51:54.575 [INF] PROT: Accepted block aaf7ef4e98724d7a871ba4161e7e8935f34b037cffe103e53681be18899623ab via relay
2021-12-02 11:51:54.604 [INF] PROT: Unorphaned block 428eea9316bdbbe31a58a8b47aeece0a89c715e1c0754ec74a50fe5b93058d65
2021-12-02 11:51:54.828 [INF] PROT: Accepted block 77986eeff4025eb8416d94d71236fe1d7a6bc6a297b8f96e13dc78659acee815 via relay
2021-12-02 11:51:56.493 [INF] PROT: Accepted block be2512d9193c4ebe045e76ed7f3de6eda0306a7cc6733353d89bda4a8fd1c29e via relay
2021-12-02 11:51:58.201 [INF] PROT: Accepted block bcf78e914439d61bc18941bb77548ee75469e980c49f6f91e9c67788a234bebe via relay
2021-12-02 11:51:58.561 [INF] PROT: Accepted block 30fcfcb1eb59ed929c9573b7c618dd7af0cc556498727ab0a8de2e23fa458b85 via relay
2021-12-02 11:51:58.582 [INF] PROT: Accepted block ab167b0c738a03de76b733437024a385144438195827bc4399ea933bddd634d6 via relay
2021-12-02 11:51:59.594 [INF] PROT: Accepted block 41377d1c4b4d3a1044c1887602fa89c43101bd209519f19ae338bf181e3bfe1e via relay
2021-12-02 11:52:01.209 [INF] BDAG: Processed 343 blocks and 16 headers in the last 11.47s (349 transactions, 2021-12-02 11:51:59.988 +0000 GMT)
2021-12-02 11:52:01.209 [INF] PROT: Accepted block 77c9ced5e1c71aec4374013c73e1bf61f055e58744b56f885eacab8b88f11088 via relay

ok, does that mean the blockchain is synced???

if i type ./kaspawallet this happens./kaspawallet
Please specify one command of: balance, broadcast, create, create-unsigned-transaction, dump-unencrypted-data, send, show-address, sign or start-daemon
or
miner2@Miner2:~/Downloads/kaspad/bin$ ./kaspawallet show-address
kaspawallet daemon is not running, start it with `kaspawallet start-daemon`
then
miner2@Miner2:~/Downloads/kaspad/bin$ ./kaspawallet start-daemon
2021-12-02 11:54:38.069 [INF] KSWD: Listening on localhost:8082
rpc error
github.com/kaspanet/kaspad/infrastructure/network/rpcclient.init
   /home/runner/work/kaspad/kaspad/infrastructure/network/rpcclient/rpcclient.go:174
runtime.doInit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/proc.go:6315
runtime.doInit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/proc.go:6292
runtime.doInit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/proc.go:6292
runtime.main
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/proc.go:208
runtime.goexit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/asm_amd64.s:1371
Method unavailable when kaspad is run without --utxoindex
github.com/kaspanet/kaspad/infrastructure/network/rpcclient.(*RPCClient).convertRPCError
   /home/runner/work/kaspad/kaspad/infrastructure/network/rpcclient/rpcclient.go:177
github.com/kaspanet/kaspad/infrastructure/network/rpcclient.(*RPCClient).GetUTXOsByAddresses
   /home/runner/work/kaspad/kaspad/infrastructure/network/rpcclient/rpc_get_utxos_by_addresses.go:17
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.(*server).collectUTXOs
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/sync.go:136
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.(*server).collectUTXOsWithLock
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/sync.go:127
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.(*server).collectUTXOsFromRecentAddresses
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/sync.go:114
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.(*server).sync
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/sync.go:34
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.Start.func1
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/server.go:68
github.com/kaspanet/kaspad/util/panics.handleSpawnedFunction
   /home/runner/work/kaspad/kaspad/util/panics/panics.go:83
github.com/kaspanet/kaspad/util/panics.GoroutineWrapperFunc.func1.1
   /home/runner/work/kaspad/kaspad/util/panics/panics.go:32
runtime.goexit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/asm_amd64.s:1371
error syncing the wallet
github.com/kaspanet/kaspad/cmd/kaspawallet/daemon/server.Start.func1
   /home/runner/work/kaspad/kaspad/cmd/kaspawallet/daemon/server/server.go:70
github.com/kaspanet/kaspad/util/panics.handleSpawnedFunction
   /home/runner/work/kaspad/kaspad/util/panics/panics.go:83
github.com/kaspanet/kaspad/util/panics.GoroutineWrapperFunc.func1.1
   /home/runner/work/kaspad/kaspad/util/panics/panics.go:32
runtime.goexit
   /opt/hostedtoolcache/go/1.16.10/x64/src/runtime/asm_amd64.s:1371

what gives

How do you run this wallet?
How do i get andress?
How do i mine
How do i check my balance?

Why are there not simple instructions in the ann....(do not ask me to go to discord, please post here so all can see)

---

Also, just tried mining using this test address

./kaspa-miner-v0.1.3-linux-amd64 --mining-address kaspa:qpyn6a3gudav4jzt0gway6tndj3tyw0uazehet5g0fvutmmnktg0zz2klk4dt
 cos mine says i have the wrong address...duh

Anyways, i get between 2-4 mhs, but the net hash is already 24GHs, so 1000 times higher...so ZERO point in solo mining.
What a terrible launch, needs pools ready or no point even trying...fail

[moderator's note: consecutive posts merged]

What are you talking about?  With a fairly basic CPU, you can easily get a couple blocks a day.

Please guide me thru how to get the wallet working first

I would recommend joining the Discord and there will be lots of folks available to help you live with wallet and mining issues.

If you read my post above detailing all the errors u have you would see that i also asked the DEV to please post any help on this ANN. Why should people have to join DISCORD just to mine his coin.

If you have managed to get your wallet working, please post the instructions here.
Most people accessing this from a work, or public PC can't go to DISCORD

I started mining using this guide, and everything works for me - https://steemit.com/crypto/@kaspa/kaspa-quick-start-guide
Block reward 500 coins.
Be careful and you will succeed)

Thankyou kindly
Worked like a charm

Hashrate is increasing because the project is promising? Mystery solved.

need help for .bat file :
1. kaspad --utxoindex
2. ????
3. kaspawallet create
4. kaspawallet start-daemon

thanks

Didn't understand what your problem is.
That's right, what exactly does not work?
Create a wallet and start mining.

I don't know when the next version will start. I hope the next version can optimize the GUI and make it easier for our new friends to mine with one click。

There are so many new people in these two days that they can't even use basic commands!

Wasn´t that hard to get mining running.

But yes it could be easyer for new crypto guys.

I just want to remind everyone that our approach in Kaspa was to involve the community ASAP. We didn't do any premines or airdrops or kept the network closed in any way, but rather announced it to the public as soon as we had a running mainnet.

As a result, engaging Kaspa at this primordial point of its existence is a bit of a DYI experience ;D We didn't have time and resources to develop GUI wallets, write extensive guides, or mount a professional looking network.

We hope these efforts will come gradually from within the community, in exchange for our efforts to make coin dispersion as egalitarian as possible.

Translating to Russian language - https://bitcointalk.org/index.php?topic=5373891.0
I will follow the development of the project and supplement the topic.

2021-12-06 13:23:49.358 [INF] CMGR: DNS discovery failed on seed n.kaspa.turkel.in: lookup n.kaspa.turkel.in: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.

if i try utxo index.
what is the problem? i have synced complete and now this

-

GPU finally came out. Now, well done!

The difficulty has increased in the past few days, and on a few days , i have not found any block.
Although earlier there were several blocks a day.

cannot sync, something is broken?

If GPU mining already killed CPU mining then the title is misleading.  ::)

I think all that happened much faster then dev anticipated.

The community is so popular that developers can't improve the development progress?

There is activate development, check github :shrug:

Three different nodes crashed with the same error

2021-12-08 01:44:38.484 [INF] CMGR: Connecting to [2a01:4f9:6a:1b23::2]:16111
2021-12-08 01:44:38.661 [INF] PROT: IBD started
2021-12-08 01:44:38.705 [INF] PROT: Downloading headers from <084146972b65c846c4ea8a41b865ecc6: 157.90.212.112:16111>
2021-12-08 01:44:39.498 [INF] CMGR: Connecting to [2a00:1e10:226:2:84b7:b1fe:ff1:946b]:16111
2021-12-08 01:44:40.503 [INF] CMGR: Connecting to [2001:14ba:3fe:9600:ed31:9795:b0e4:4637]:16111
2021-12-08 01:44:40.569 [INF] PROT: IBD finished (interrupted)
2021-12-08 01:44:40.570 [CRT] PROT: Exiting: Fatal error in goroutine `flow-HandleRelayInvs 35`: not found

---

If you delete the node and download it again, a strange thing happens. It has been pumping the blocks for December 6 in a circle for 24 hours.
It looks like this coin is a complete scam, gentlemen.

[moderator's note: consecutive posts merged]

Don't tell him why this is the case. This is the unique skill of the project. It's more advantageous for fewer people to compete for mining. Because there are too many people involved now, I can't dig out the block. It's better for fewer people to compete with us, so that we can harvest more every day, isn't it?

If now the new node is not started because it crashes when downloading blocks, now only those who downloaded the working blockchain earlier are mining. Discrimination?

Judging by the increase in the hash rate, mining is carried out on video cards
but there was no announcement of the miner for the GPU.
Someone mines with a private miner.
The value of the coin is highly questionable and there is no question of fair distribution.

Third party developers in the community have voluntarily contributed GPU tools. If you pay attention to the discord server, you must know this tool. Is it fair? All over again is to fight for it by yourself, not wait here!

Kaspa's official website has a link to discord server. Those who are interested can pay attention!

This is a community project, no ICO, no hype

Why can't  announcements here on the forum?
Why are so many newbies shilling a coin?
Is the coin not interesting to the old-timers of the forum?

This BCT thread was created by a community member who said they would maintain it and has since vanished, it was not created by the core team, and we are too busy to update it. The Discord server is our main outlet for core team and community update. Since we have no premine etc. we have no funds to hire fancy PR and marketing teams, so it is up to the users to stay updated. As I said, since this is a community project it is more of a DIY experience  :)

I will make a post in the Discord asking community members to try and better maintain the BCT thread, but I can't guarantee anything.

Why are new nodes not working? Launched on different computers. Dropping with the same errors?

Brother, I know your trick. Release negative information to cause panic so that retail investors can sell coins. You can buy KAS at a very low price, right? That's smart. Let's talk in private. Let's make a friend!

Aren't you the same guy that a few replies ago lied about the fact that the coin is in test net

https://steemit.com/mining/@kaspa/opensource-gpu-miner-for-nvidia-has-come-out

there is a link to github on open source CUDA miner, no info on OpenCL miner though.

premining has many forms LOL

Decentralized, 1 second POW coin... With an aim of 100/blocks/sec (!)

Consider me in!

Does the core team give a specific hard bifurcation time? I'm eager for 10 blocks or even 100 blocks per second. How cool this POW scene will be!

In a sense, Kaspa does not aim to become another member of PoW coins but to replace an existing one — Litecoin. Litecoin was supposed to be the silver to Bitcoin’s gold, so we were told. However, it turned out to be quite totally useless, and provided no meaningful functionality over Bitcoin-it is essentially a basket of minor parameter changes from Bitcoin. From the perspective of a 2020 end-user, there’s no major difference between waiting for 15 minutes and waiting for an hour; both are equivalent forms of “forever.”

https://hashdag.medium.com/in-which-i-run-with-the-ghosts-of-my-hometown-95ad503c88c (https://hashdag.medium.com/in-which-i-run-with-the-ghosts-of-my-hometown-95ad503c88c)

Those who think everything should be spoon-fed to them and are griping when it is not are doing those of us who pay attention a great favor.

They are staying away.  They have nothing to add. 

There is an explorer (http://katnip.kaspanet.org) it might need a lot more work but there is nothing "improper" about it.


Had you read the thread you would have known that we implement block pruning, which means that there is no genesis block. The oldest stored block is three days old. Alongside we keep the UTXO set of that block and a cryptographic proof that this is indeed the UTXO set of a chain of that weight. This proof is an adaptation of the techniques developed here: https://eprint.iacr.org/2021/623.pdf


Like in most coins, any person can derive virtually infinitely many public keys for their wallet, and it is infeasible to tell whether two addresses belong to the same wallet. Therefore, "whale wallets" and "rich lists" are garbage information and are useless to track.


Due to the high block rate, home GPU and even CPU miners can still mine and expect their fair share. Even at three times the current hash rate, a single average home CPU can mine a block every three days or so, which means that if they mine for just a few weeks they will almost surely get their expected share without having to join a pool (for example, if Bitcoin had the same hash rate, then the same user would have to wait about 5 years before they see their first block, which means they would have to mine for decades to get close to their expected share). The fact that solo mining is still profitable in increasing hash rates is a feature, not a bug. When we reach a hash rate where pools make sense, they will be created by the community. If anything, the lack of pools indicates that the coin spread is more egalitarian. Pooling is a necessity which rises when the expected time for a single block for the average user becomes huge. After we increase the block rate to 100 bps, even if we ever reach Bitcoin magnitude of hash rate (which we won't even in the fantasy script where we become as popular as Bitcoin, as our hash is much heavier), very small pools would still be profitable. If


GPU miner is community driven, currently we don't have reason to suspect covert optimized miner. If in the future we will suspect differently we might try to help the community improve their miner. None of us is a GPU developer, and we have no reason to believe we can optimize the miner better than the community.


I don't use Word, I use vscode. The website is ugly, yes, thanks for the valuable input. I updated it. It is still ugly but now it include links to both HH and GPU miner. At least one of your comments wasn't useless.



We prioritize stabilizing the node, stress testing and increasing the block rate over listing and PR. It makes sense to us that we get a firm grip of the capabilities of our coin before making extravagant claims or encouraging people to sink their money into it. We know that it is very common in the crypto world to make baseless claims and worrying about partially covering them later, but we have a different approach. That being said, any community driven PR efforts are welcome.


If you are going to make baseless accusations, at least go with accusations that make sense. If we just wanted to fill our bag and pump the coin in exchanges we would not have chosen a fair launch model. We'd premine the shit out of the coin and then list it ASAP. If you see our careful conduct as an attempt to make a quick buck, then your conclusion was probably predetermined.

Whats your point, why are you here, whats your angle, people dont attack a project without a motive. If you think this project is a joke, then make your statement and go away. By hanging around its like you have other motives. I have been in this game a long time, seen many people come out spouting crap they think will happen with a project and what its downfall will be, guess what 95% of the time its just talk. Your statement on FPGA's while sounds like we should all be scared is just factually WRONG. Who is going to make that "slight modification" you.... good luck!! FPGA are a full time job just to keep running on existing heavyhash networks. Will they come, maybe someday, but i dont see that anytime in the near future.

The community around this project is alot brighter than you might think. 

Gentlemen developers, are you going to fix the memory leak in the client?
Under Windows, it takes all free RAM and stops working, in the system there is 24 GB of RAM.

He's just a FUD troll (seriously, check out his posting history) who can't spurt a single sentence without contradiction themselves. On one hand, our GPU miner is shitty beyond reason while oBTC's is awesome, on the other hand the oBTC FPGA miner "only requires a small modification". So when considering GPU, the miners are completely different and cannot be adapted easily, but when considering FPGA, the difference suddenly becomes "a simple modification"? Sure buddy you make a lot of sense and exhibit superior consistency.

Yeah, I obviously lack "skill" as is reflected by my lack of familiarity with Discord features. Discord boosts are obviously quintessential knowledge for any cryptocurrency designer and developer and not being familiar with them indicates general incapability  :D :D :D

(I won't respond to your other "points" as I already addressed some of them and the rest are just blatant lies)

I addressed each and every one of these points (though I will have an update regarding 1) in a couple of days). You just ignored everything I said and called it a "bunch of excuses" proving that responding to you is a waste of energy.

The blatant lie was "discord dev wallet holders didnt know why blocks need confirmation etc. ".

You have consistently proven that you are just looking to undermine us at all costs rather than having this discussion in good faith, so I am not going to reply to you any longer.

At present, it seems that only N graphics card can dig. I hope the mining program of A graphics card can come out as soon as possible!

An update and some clarifications

Update: a new version of the GPU miner has been released which improves CUDA mining performance by about 250%. It also finally introduces support for OpenCL, though it requires much more testing and optimization to be competitive.

Clarification: Despite the impression that some FUD trolls are trying to make, a large amount of red tips (as in a picture posted above) has literally nothing to do with a "51% attack", or any form of viable attack.

Red blocks are blocks which are disconnected from most of the network, they occur in several scenarios. In particular, a block which points to a very old block will be red. The picture above is the consequence of a scenario where a miner kept posting blocks pointing at old blocks (e.g. because they are getting templates from an out of sync node without realizing).

The picture is a few weeks old, where we first encountered such a scenario and realized that red tips posed a slight issue due to some bottlenecks in our reachability mechanism (that is, the mechanism which efficiently calculates whether one block is in the past of another block. This ingenious feat of CS theory and software engineering -- which actually solves a known open problem in a broad family of special cases -- was crafted by msutton, the same person which a certain FUD troll has tried to portray as someone who "does not understand why confirmations are needed" lol).

These bottlenecks have been fixed two versions ago and have been thoroughly tested against amounts of red tips two orders of magnitudes larger than the picture.

Every once in a while an inattentive miner does cause an increase in red tips and this has not caused nodes to increase CPU usage, whereby spamming red blocks is not even a viable CPU attack anymore (not to mention a "51% attack").

People who infer that a couple of hundred of red tips imply a 51% attack probably haven't even a vague understanding of GHOSTDAG and could be safely ignored (this argument is easily quantifiable. Red tips can be as old as three days before they pass the pruning point and get deleted. Our network makes one block per seconds, so a pruning Window is about 250K blocks. In the scenario depicted in the photo, there were about 500 red tips. Hence, to create this amount of red tips it suffices to hold about 0.2% of the global hash rate, which we agree is quite far from 51%).

Just to be clear, even in the old "problematic" version, in order to actually choke nodes on CPU attack the adversary would have had to waste hashes equivalent to at least 1k blocks (though, in the difficulty target of three days ago, so it might be slightly cheaper than 1000 current blocks). After the update this seems to not be a concern even if an attacker spams ten times that much and more, even for nodes running on weak CPUs. We have no indications that any amount of red tips poses an issue.

For more details, you are welcome to peruse the lengthy discussions we had about this issue in our Discord server.

just for me, to understand your point of you: if a community project with no hype, no marketing, no nothing, just software developers working on code, starts running within its community (which is following the project since at least one year) but without an announcement on this forum, it means that the target of the project community is "premining"?

seriously?  

---

your strategy to "talking about your project problems" is:
1. take a random screenshot of a single message, place it out of context and state that "it's proving something" (your first point on the message above;
2. take a random screenshot of the network correctly reacting to a wrong operation of a miner and describe the situation as "your network have been 51% attacked and you didn't even know that". (second point on the message above).

well.

i feel that, if your target is to troll, the approach you're offering is perfect.

but.

if you are looking for a constructive discussion about the project with developers, supporters, etc, maybe you should at least:
1. propose you question, doubt and critics in a decent way, so everyone can extract some value from these discussions;
2. if you want to sh*t on something, at least study what you are talking about first; otherwise, you seems just a little bit s*upid.

thank you for your time.

i'm sure that, from now on, we'll read a lot of interesting discussion and arguments from you.

This is the type of shitcoin that won't make you folks any money.

Just scam artist with claims of "tech" LOL

Tech tech..premine..tech. Then Dump! LOL

Do you have any actual critique of the tech? Our claims are very clear, can you point out which of them are "scam"? Does our code not do what we claim that it does? Are there any other coins which achieve what our tech already achieves (e.g. immediate confirmations on a pure POW chain)? I am all ears as to why you refer to me as a "scam artist".

i remember that discussions on this forum were bringing way more value on people reading, studying and learning.

and i'm kind of surprised that an account flagged as "legendary" waste its time with statements with no value like that.

As a casual observer not affiliated with the project in anyway I have to say that Kaspa is one of the most promising projects I've come across in my 5 years of exploring crypto. There is a sea of crap out there so it's refreshing to find a project that offers not only unique tech but also strives to uphold the OG philosophical roots of crypto, keeping things as decentralized as possible. I came across the work of daglabs from a coindesk article written in 2018 and was intrigued enough to follow their research and development  to the eventual launching of Kaspa. If it's a con it's a really, really, really, long con... "Kaspa is a community project, completely open source, no central governance, no biz model. The mainnet was openly launched without premining or any other preallocation of coins." There was no premine if you did even a little research you would find that the devs try to keep everything as transparent as possible with the community. Will it make folks money? No one can know that for sure but so far things are looking great IMO.

heard and seen it all

now this is the killer quote..


you have to have coins to dump on unsuspecting newbs to make money that's how you make money. idiot

Haha, Wow I'm sorry I didn't realize i was talking to a legendary piece of shit! You are a true shit poster and I bow down before your porcelain throne. Why don't you enlighten all us noob's with your turd ass and lay down some good reasons why this project's tech is terrible, was premined, and a scam? I'm sure they are there, I believe in you!!! You are more than the sum of the generic copy paste troll comments you leave.

I'll level with you, obviously I'm interested in the project as a potential investor and I'd love to hear your negative reasons for not "digging" it. If I had to assume I would say, you are either a simple troll, or apart of a competing agenda, but who knows? Maybe I'm being too pessimistic. Maybe, just maybe you really have everyones best interest at heart (which is so kind of you). SO PLEASE, I'M BEGGING YOU! YOU FECAL SOAKED LEGEND, PLEASE HAVE MERCY ON ME AND GIVE ME THE KNOWLEDGE TO MAKE AN INFORMED DECISION BEFORE I MAKE A TERRIBLE MISTAKE INVESTING IN KASPA! Just do me and others the simple privilege of at least posting a complete thought or forming a complete argument when you lay down your profound blah, blah.

Is there a GUI miner?

No and no plans for that now that I'm aware. Recent command line tool is just about as simple as other GPU mining software. The discord also has a several helpful people if users run into problems.

Check out his post history, he is "legendary" because he helps people build rigs. No reason to believe he has any more grasp of the theory of cryptocurrencies than his, erm, porcelain throne. If he weren't a coward looking to stir up shit he'd respond to my very reasonable questions instead of picking fights with bystanders.

I've been shitcoining long before i help people build rigs LOL

Tech? LOL the "tech narrative" or "in it for the tech" LOL

You folks are the one who claimed to have invested because of the tech, now tell us how are we gonna get rich from it?

Your answer: i dunno? or you don't want to say? Because... Hehe

I already know your words even before you open your mouth, your shilling techniques are low quality and won't work LOL

still nothing useful in this discussion. for anyone.

let's hope there will be some nice valuable discussion here, in the future.

Hi, glad to join the team as Graphic designer/animator (design, NFT projects, templates, 3D animations...)
 ;) ;) ;)

fuck!   hashrate  1T/s

fuck,amd can not dig ,why hashrath 1.4T/h  now?

AMD miner released long time ago, get the head out of your a..

The technical fundamentals of this project are very good. I switched all my mining machines to mine kaspa. Only by being an early user can I have a chance to become a small whale ;D

are you  sure？

 :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D :D

上海矿工发来贺电！

我信你个鬼，糟老头子坏的很！

Hi, just came in to reply one last time to clarify that I decided to abandon this thread completely.

Making empty accusations is easy, and some people here are bored enough to make them indefinitely. We have more important things to do than to debunk accusations made by people who don't even bother to read our replies.

If anyone has doubt about the viability of our project or thinks that it is a "scam", they are more than welcome to seek us out on Discord and see for themselves. or just move on to the next coin. I believe I left enough information in this thread to establish how serious this project is. Hence, I see no point in replying any longer.

I decided to desert this thread too. If anyone thinks I am in some measure affiliated with the project or have coveted bias about it, the answer is no. I am just a a sideliner guy in the crypto lounge room. Feel free to shoot ur offers, etc. how much u are willing to pay to incentivize me to take over this project. People are blind if they can not see the reason it was abandoned.

Here's a fun vid about what makes Kaspa unique! A solid introduction for anyone interested in the project. https://www.youtube.com/watch?v=TPmW9gCeUeg

Thats Right Tito!!!

Great vid!!

If you just found this page, come and jump on this ground floor opportunity wagon,

How often do you find a PURE POW coin with 1 second confirm times and HARVARD PhD Devs that have NO PREMINE?!?!?!

Anyone talkin' shit is either super-JEL or Re-Tarded - flat out the only 2 possibilities

Come get in DISCORD or TG and start mining!!

https://discord.gg/bxpkggDNeG


https://t.me/kaspaenglish


The goal of this project is to become what Litecoin $LTC was supposed to be but FAILED - the daily tx coin!!!

Basically an $XRP that has NO BANKS OR CORPS behind it and is 110% FOR THE PEOPLE by THE PEOPLE!!!!!!!!!!!!!

First of all, it checks all the standard boxes:

pure POW
no PREMINE
NO ICO

Plus, it originated from DEVS who it was THEIR OWN IDEA . . they are not HIRED by someone else or a corporation

In my experience, the best projects are made by DEVS with a vision, and they are into the coin WAY MORE than anyone you could ever PAY to work on it

Its their BABY   . .  in other words

Otherwise - when the money runs out, the DEVS disappear, OR . . there is a problem,
and they expand the time it takes to solve because they dont really care about the chain or the coin, they just want their pay until the next opportunity comes around

DEVS who have their own project and its their baby, will stay up 4 days in a row geeking out until something is fixed, etc.

NOW  - there are all grades of developers out there - from hack cut and paste QT wallet, change supply and block time and name and logo,  create a genesis block and POOOF!  nEw cOiNzorZ!!!!!!!!!!!

Then you got guys with network backgrounds and programming that can do better than that, they make some decent changes and find a niche for their coin and they do OK
THEN . . you got these guys here from $KASPA, the rare mathematic genius level , not only that, but HIGHly educated . . they dedicated their "young man years" to school . . PERIOD . . i mean these guys have been going to school non stop for 30 years +

and its a GROUP - not just a solitary wizard behind the curtain

so guys like THIS . . not only make subtle changes to bitcoin based tech, they realllly reallllllly understand and see what the completely NEXT thing should be , AND they are capable of turning it into a reality

Hi Everyone!

 
kaspad v0.11.14 is out: https://github.com/kaspanet/kaspad/releases/tag/v0.11.14

This release has no major updates, but it includes an important bug fix to the new IBD flow introduced at v0.11.13. So it is highly recommended to upgrade. Keep the same DB etc. and simply rerun kaspad with the new version.

Our roadmap for the coming week or two includes a few large features:
* The much anticipated core wallet auto-compound feature by @svarog
* Reachability DB migration by @someone235  -- an internal migration and optimization which improves performance (of both header processing and storage) noticeably
* Optimizations for  "pruning point anticone" processing (effects fresh-syncing nodes)


GitHub
Release v0.11.14 · kaspanet/kaspad
Fixed a bug in the new IBD chain negotiation protocol (#1981)
Release v0.11.14 · kaspanet/kaspad

Intresting project, i'll definetely be following it and seeing what it becomes over time

someone235 — 03/25/2022


Unfortunately, @Stas, the maintainer of KGI and kasboard, is no longer taking part in this project (see his message here https://discord.com/channels/599153230659846165/755890250643144788/956850666096197692 ).
But this can be a great opportunity for any developer here to step in and replace him in one of those projects. The projects require relatively small understanding of the Kaspa ecosystem (if you'll compare it to core development and mining), so I believe anyone with experience with React (for KGI) or Grafana (for kasboard) will be able to do the job.
So if anyone is interested let me know and I'll try to help him with the onboarding process.

P.S.
Not sure how yet, but I also think that the devfund should incentivize such activity. But I think I wanna see who's interested in taking the job before we discuss the details.

13
March 27, 2022

svarog — Today at 12:02 PM


Hey all!

Go 1.18 has released, and we're very excited to finally start using Generics.

We will upgrade all kaspanet repositories to depend on go 1.18 starting in 3 days - Wednesday March 30th.

If you plan to compile any kaspanet repositories, including kaspad - please upgrade your Go toolchain by then.

Freshman — Today at 11:39 AM
@everyone Hello Kaspers!

Welcome to the first community funding pool!

The proposal behind this pool is to get $KAS listed on the crypto exchange txbit.io.

Txbit.io is fully integrated on the most important crypto listing pages such as Coinmarketcap, Coingecko and the portfolio tracking app FTX (former Blockfolio).

A listing on Txbit would bring us the opportunity to get listed on these crypto pages as well. It would also increase the chances to get listed on other exchanges.

As there is no other exchange listing yet, a listing on txbit.io would also provide a secured environment for buying/selling activities.

We got the following offer:

-2000$ to be paid in a stablecoin.

-They told us that Kaspa could be listed within two weeks after the payment has been made. (Please keep in mind that this is just an estimation. There could always be some unforeseen issues)

The goal for this pool has been set at 2100$ to cover all potencial fees. If there is some money from the additional 100$ left, we would use it to help filling another community funding pool in the future.

The duration for this pool is 2 weeks (Until April 10th, 8pm CET). If we miss the necessary cap, everyone would get refunded.

Supported Currencies: BUSD (BEP20) or USDT (BEP20) only

Thank you very much for your support!  

Link to the pool: https://app.poolo.io/pool/ed4fd934-7280-4e37-b43d-bc3538175947

If you have any questions, feel free to ask in the #funding-pool-discussions channel

---

***UPDATE***

Funding for first listing now at 77% in less than 24 hours!!

$1617 of $2100 so far!!


https://app.poolo.io/pool/ed4fd934-7280-4e37-b43d-bc3538175947

Freshman — Yesterday at 12:38 PM


Hello Kaspers!

I'm happy to announce that the community funding pool for the listing on txbit.io has been successfully filled!

The payment for the listing is already done. I shared the Transaction ID and the receiving confirmation from txbit in the #funding-pool-discussions channel

Thanks to everyone who helped reaching this goal in less than 24 hours!

I'll share all minor updates regarding the listing in the #funding-pool-discussions channel as well.

The listing itself will be announced through the official announcement channel.

You need to ask yourself ONE question -  Can your other coins Lead Dev do this?


******************************************************************

hashdag — Today at 5:47 AM

@someone235 IIRC we thought SPV design would be much more complicated in DAG than in chain due to double spends, but we can simply provide inclusion proof of the utxo in the merkle root of accepted txns (or utxos) by the merging block, and then the SPV needs either to (i) run GHOSTDAG to convince itself that this is indeed the merging block, or simpler yet (ii) require inclusion proof for a few candidate merging blocks, and if the utxo is accepted by all of them

Announcement for miner developers:

The following PR (https://github.com/kaspanet/kaspad/pull/1988) added a new event type to the RPC API, dedicated for miners.
The event is named NewBlockTemplate. (https://github.com/kaspanet/kaspad/blob/dev/infrastructure/network/netadapter/server/grpcserver/protowire/rpc.md#notifynewblocktemplaterequestmessage)

Miner software should replace the current BlockAdded event with this event.
This event is called only when the real conditions for a block template update were met (for instance a block can be added to the DAG but is not always
added as parent of virtual due to various mining rules). Additionally, we avoid calling this event during IBD when thousands of blocks are added to the DAG
every second, and in the future we might trigger this event also as a result of mempool changes.

I'm implementing several more optimizations for the miner-kaspad communication cycle, including template caching, and modifying
"out of sync"/isSynced definition such that miners will mine under all possible circumstances.

Hence our recommendations for miners are the following:
- Register to the new event type (perhaps verify that kaspad version >= 0.11.15 or simply try and if you error fallback to prev event)
   -- As a reference, the registration was updated in the native go miner already https://github.com/kaspanet/kaspad/blob/dev/cmd/kaspaminer/client.go#L33
- If the template you get is marked isSynced=false, do not mine, we will indicate this only when the node is really behind (unlike now).
- If you do decide to mine even if isSynced=false, use the latest template you just received and not anything older

@someone235 @hauntedcook @demisrael @iedoc @elichai2  @Community Developer
GitHub
Optimize the miner-kaspad flow and latency by michaelsutton · Pull ...
This PR includes initial changes to improve the miner-to-kaspad communication cycle, including the following:

A dedicated "new block template" event for notifying miners only when necess...
Optimize the miner-kaspad flow and latency by michaelsutton · Pull ...
GitHub
kaspad/client.go at dev · kaspanet/kaspad
Kaspad is the reference full node Kaspa implementation written in Go (golang). - kaspad/client.go at dev · kaspanet/kaspad
kaspad/client.go at dev · kaspanet/kaspad

Hey guys look at this great short on youtube from the Chinese KAS community:


https://youtu.be/YZz9OrY1e14

Yahooooooooooooooo!

Here we have Good Ol' SonofaTech (175k sub) YouTube with an very informative section on KASPA starting around 6:30



https://www.youtube.com/watch?v=xUjPnbH7jeA

aspect — Today at 10:53 AM


KDX 2.9.1 is out at https://kdx.app/   (next release we will start releasing on Github as well). This is an intermediate release - it fixes the KDX application exit bug when the application is set to a language other than English.  It also addresses some issues with i18n translations.  This version now properly handles translations and upon completion of KDX translations, they will be made available on the PWA as well (web app).

Thx to SonOfaTech (175k) for posting a $KASPA clip on Youtube !!!

https://t.co/VQu7QdTic2

$KAS mining calc!!


https://minerstat.com/coin/KAS

hauntedcook — Today at 11:17 AM


Hi all,
The long miner awaited version v0.2.1-GPU-0.5 is finally out. This version includes stratum support, Cuda OC settings, and most important - uses the new events from kaspad, allowing for smoother IBD, and less resyncing time.

This version include some changes to how the events are processed. If you see drop in performance, please report the details
https://github.com/tmrlvi/kaspa-miner/releases/tag/v0.2.1-GPU-0.5

Here's some integration status with TxBit - since KASPA is a brand new tech, the integration team from TxBit has some questions and the KASPA Devs contemplating possible solutions:

*****************************************************

Got some requests from TxBit, will appreciate your take on things:


Hi Mike! Thank you for writing these examples. We have a couple of questions about the API:

- GetUTXOsByAddressExample
The 'GetUTXOsByAddressExample' call seems to require one or more addresses in the 'GetUtxosByAddressesRequestMessage'. The method returns all possible UTXOs for that (array of) address(es). This method would not work very well on a larger scale, like our exchange. Say that we have 10k addresses and 100k transactions. It would be really inefficient if we call this method for each address and get back all UTXOs. Our questions are:
1) Would it be possible to provide us with an API endpoint that:
a) returns transactions instead of UTXOs?
b) returns only an incremental list of transactions?
c) does not require us to specify an address but instead returns the data for all addresses in that wallet that have UTXOs?
For example, the Bitcoin API call "listtransactions" does precisely that.

- CreateUnsignedTransactionExample, BroadcastTransaction, and transaction signing
Our questions are:
1) Would it be possible to provide us with an API endpoint that:
a) works like the Bitcoin API method "sendtoaddress"?

We can not work with manual signing. Our workflow is completely automated.
About CreateUnsignedTransactions:
 I think about providing a mode of operation in daemon that will ask for password on start / cli, and than will enable Send and Sign requests.

Another option is to add a Sign and Send commands to kaspawallet that will take a password. <- this is easier.
About GetUTXOsByAddress:
a. We can't provide transactions, that's fine by them.
b+c.  I guess we can add a GetUTXOs to daemon that will get UTXOs for all registered addresses.
Then we'll also need to add to GetUTXOs both in kaspad and in daemon a parameter of "startingFromDAAScore", that will filter out UTXOs above certain DAAScore.
I'm not very sure we want this functionality in kaspad. Does maybe Katnip support such things?

*********************************************

msutton — Today at 1:37 PM


Hey everyone @here , let's have a live experiment. We have a nice-size sidechain now. We also have an RC version (RC=release candidate) running for a few days by our dear @Validators , which remains synced despite side chains. So if your node is going in and out of IBD, please redirect your miner to one of the following IPs, provided generously by @Tiram

144.76.19.91:30510
23.88.70.20:30510
116.202.130.71:30510
135.181.177.189:30510


this will be a nice test for the new version in terms of both, staying synced and mining, and stretching the load over these nodes.

Edit: ideally you should use the new miner version for this because it communicates with kaspad better at such times

https://github.com/tmrlvi/kaspa-miner/releases/tag/v0.2.1-GPU-0.5

msutton — Today at 3:00 PM

Kaspad11.15 -

it's pre-released under my kaspad fork. Tomorrow morning I'll release an official version + upgrade instructions (it's not a simple upgrade this time)

Hi @everyone


kaspad v0.11.15 is out: https://github.com/kaspanet/kaspad/releases/tag/v0.11.15

TL;DR
Auto-compound wallet feature, improved miner-node flow, big performance improvement in header processing (requires a DB upgrade, read instructions below).

Full details:
* Add auto-compound support for Kaspawallet: if a transaction's mass is too-high, kaspawallet will split the transaction into multiple smaller transactions.
* Unite reachability data to a single storage entity: improves performance of header processing and saves DB space. Requires a DB migration or a fresh sync.
* Improved miner-node flow, including: (i) new new template event, dedicated for miners (both community and bz miner already support this), (ii) cache for block templates to support many miners over a single kaspad more efficiently, and (iii) fixed definition of "out of sync" to keep the network up and mining also during side-chain IBDs
* Upgrade to go 1.18 and removal of v4 p2p version
* Many more small bug fixes and improvements

Upgrade instructions:
* The fastest is to sync from fresh into a new DB, and then switch. This option is also faster and also avoids down-time of your node. Do the following:
// Run the new v0.11.15 kaspad with a new DB directory and non-default ports:
kaspad --utxoindex --appdir="<new dir>" --listen=0.0.0.0:26111 --rpclisten=0.0.0.0:26110
// Once synced, shutdown both nodes, move <new dir> to replace the content of <default dir> and rerun the usual node.
// Make sure you use the new binary here too
kaspad --utxoindex

* The other option is to simply rerun your usual command with the new version. This will start an in-place DB migration process that takes longer than fresh sync depending on the size of your DB.
NOTE: if you maintain an archival node, this will delete the history, so backup the archive DB before.
GitHub
Release v0.11.15 · kaspanet/kaspad
What's Changed

Add support for auto-compound in kaspawallet send (#1951)
Unite reachability stores (#1963, #1993, #2001)
Add names to nameless routes (#1986)
Optimize the miner-kaspad flow and...

Recording from last R&D Meeting:


https://us02web.zoom.us/rec/share/IkalJgToJ3s4_-_v3WJP9TVKyo7JrWhtXsQfSsQRXeRalXz-q4SzAm-Eznprz8Nj.CyM7fijsCVxifU5M Passcode: #79?#jGl


Zoom Video Communications

Devs geeking out to add commands to KASPA WALLET for TxBit - our first exchange!!


Kaspawallet daemon: Add Send and Sign commands by svarogg · Pull Re...
This PR adds the Send and Sign commands to the kaspawallet daemon, to be used by external wallets and APIs.
Requested by TxBit exchange.



https://github.com/kaspanet/kaspad/pull/2016

奇怪啊，昨天的回帖没了，回档了？

@everyone


Kaspad v0.12.0 is out: https://github.com/kaspanet/kaspad/releases/tag/v0.12.0
This upgrade is mandatory. It contains a hard fork at DAA score 14687583 (estimated to be on 28/04 16:38 UTC). Everyone who doesn't upgrade will be split off the network.
The main focus of the hard fork is to address the issue of deep side chains that spam the network. After the hard fork is activated such side chains will be ignored unless they win the block race and have more blue work than the rest of the network. The hard fork also removes the previous limit on transactions to send less than 21M KAS.
Note: whoever who's upgrading directly from v0.11.14 might experience a very long DB migration process, so in that case I would recommend to just delete the old data directory and resync from scratch.

P.S.
We contacted @aspect and he said that a new corresponding KDX version will be released in the next two days.


GitHub


This version contains a hard fork at DAA score 14687583 (estimated to be on 28/04 16:38 UTC). Upgrade is mandatory, and everyone who doesn't upgrade will be split off the network.
The main focus of the hard fork is to address the issue of deep side chains that spam the network. After the hard fork is activated such side chains will be ignored unless they win the block race and have more blue work than the rest of the network.

Changelog
Breaking changes:
Hard-fork at DAA score 14687583 (estimated to be on 28/04 16:38 UTC) which includes:
* Using separate depth than finality depth for merge set calculations (#2013)
* Not counting the header size as part of the block mass (#2013)
* Increasing block version to 1 (#2013)
* Removing the limit on amount of KAS that can be sent in one transaction (#2013)

Bug fixes:

Making a workaround for the UTXO diff child bug (#2020)
Use cosigner index 0 for read only wallets (#2014)
Non-breaking changes:

Adding a "sweep" command to kaspawallet (#2018)
Use blue work heuristic to skip irrelevant relay blocks
Kaspawallet daemon: Add Send and Sign commands (#2016)
New Contributors
@D-Stacks made their first contribution in #2018
Full Changelog: v0.11.17...v0.12.0

2 Pull Requests for TxBit integration


 - 2 Pull Requests for TxBit integration


9 PRs from mostly non-core devs as well!

https://preview.redd.it/wejrdpbgi4u81.jpg?width=787&format=pjpg&auto=webp&s=5c2e6512adea1b56c09b913a4ec47db515cc74d1

hauntedcook [kaspa-miner-GPU] — Today at 1:47 PM


Kaspa-Miner version 0.2.1-GPU-0.6 was released, continuing our tradition of making file names really long.

This is a stability release, which fixes issues with miner not working for certain drivers and installations. Also, we finally report hashrates per device (this isn't implemented in hiveos scripts yet), and lower the miner memory footprint for CUDA.

The overclock capability is included only in overclock release, since we require newer nvidia drivers (495+) for it.


https://github.com/tmrlvi/kaspa-miner/releases/tag/v0.2.1-GPU-0.6

As of this moment the net is at 14,483,141 DAA score, with the target HF time being 14,687,583.

This leaves us with ~56=(14687583 - 14483141)/3600 hours to the countdown, which is pretty much on schedule



^This was 8 hours ago from RIGHT MEOW!!!

So that means 2 days even until the Hard Fork!!

The Hard Fork introduces these new features:

Breaking changes:

Hard-fork at DAA score 14687583 (estimated to be on 28/04 16:38 UTC) which includes:
* Using separate depth than finality depth for merge set calculations (#2013)
* Not counting the header size as part of the block mass (#2013)
* Increasing block version to 1 (#2013)
* Removing the limit on amount of KAS that can be sent in one transaction (#2013)

Kaspa in now listed on two exchanges, https://www.exbitron.com/ and https://txbit.io/

My reff links if someone would like to register:
https://www.exbitron.com/signup?refid=IDF3B9B52D60 (https://www.exbitron.com/signup?refid=IDF3B9B52D60)
https://txbit.io/?r=24eb6 (https://txbit.io/?r=24eb6)

Good Luck :)

KASPA coin is good for GPU mining, but there is a little bit hot algo for summer. There is a review of KAS here: https://www.cryptoprofi.info/?p=11997. Taking into account activity of developers, this crypto may have good future.

Really great algo. Thank you devs. More pools in the future hopefully. :)

Any guide to engineer a FPGA miner for this?
I'm already running my own node on GPU and wish to expand with FPGA :)

Thank you and keep up the good work!

Your best bet is to head on over to the Discord (link on https://kaspa.org (https://kaspa.org)) and talk to people about it there.

Hi. Is there a faucet claim limit? There seems to be that limit.

At least from the wallet, the daily faucet limit is 5 KAS.

Use a vpn and change your ip. Login again and reclaim the faucet. Can do it lot of time. I’ve done it 20 time before  getting bored

This is exactly why there's a limit and probably why it will be removed altogether in the future.
in short this is why we cant have nice things.

That's because bad design, faucet should credit enough for 1/2 tx, not give something away that is actually worth more then that.

Hoвoe этo xopoшo зaбытoe cтapoe.
Кacпa этo cкopee вceгo пoпыткa пepeзaпycтить или peaнимиpoвaть cтapый пpoeкт.
Heтy бyдyщeгo y тaкиx пpoeктoв, вoт нaглядный пpимep https://nerva.one/ Nerva (XNV)

Would like use my A10 750 miner to mine KAS

it is possible to mine just KAS or only merge mine with ETC??

I'm pretty sure those ASICS are not compatible with the iteration of HeavyHash as Kaspa uses.
Correct me if i'm wrong.

Updated OP with pool links and exchanges, and other link updates.

Console wallet latest version, when trying to send coins, issues: chacha20poly1305: message authentication failed

Strong Community!! Very good project, very promising !!!!

Just so everyone is aware, Kaspa is now trading on MEXC with a USDT pair. Their first Tier 1-ish exchange. It's good to not have to use txbit or Exbitron anymore.

https://www.mexc.com/exchange/KAS_USDT

I've been in this one for a few months. The potential of the PHANTOM GHOSTDAG protocol is huge.

Unfortunately there was a big reduction from 5 to 1 KAS. Perhaps it's related to these abuses or entirely the big new exchanges that have listed or are about to list KAS.

Exchanges it is trading on are to impose high taxes on in / out transfers. Take ur money out before u can not. They run software that spoof trades, they act misleadingly to ur asses. The truth has transpired that someone stole the allocations from community treasuries. When funds are locked in a decentralized autonomous community it is always a concern to wary investors as regards safety of the fund backing the underlying security.

prove it, or GTFO.

Same applies to you about disproving and it would look better than this rage comment. You would be better to dissect his/her argument and disclaim it thoroughly. Angry reaction is always a takeaway.  
Sometimes exchanges do these shady practices by themselves with trading fee/withdraw fee/deposit fee etc.. So it can mean a lot of things.

I am more interested in: Do you have a huge pre-mine "locked"? Well that's generally a red flag, so he/she has got a point.

0 premine

mate, your ideology is flawed. I am not the one who needs to disprove anything. User comes here spreading stupid unresearched FUD, they gonna get burned.
I have no skin in this game apart from being a miner of Kaspa.

Early mining was exceptionally rewarding on CPU and it was easy for anyone to stack up millions of Kaspa.
This is the best method to create a fair launch of any POW coin and you are correct, there was 0 premine done by the dev team.

to note, I mined 4million kaspa at the start and I'm not a member of the Kaspa team. I merely mine it, and OP this thread.

How is it flawed? There are several parties/sides in crypto "game". I don't think in extremities and black and white: "I am right and don't have to debate, while he is FUD". He made accusations, that's one step higher than simple FUD and needs to be combated/disproved. Crypto is a constant struggle and in motion all the time, you cant just lay back.

No one stole anything. You are just lying. DevFund wallet is here:

https://explorer.kaspa.org/addresses/kaspa:precqv0krj3r6uyyfa36ga7s0u9jct0v4wg8ctsfde2gkrsgwgw8jgxfzfc98

All community donations. The wallet is managed by 4 members of the community (msutton, Tim, The SheepCat and demisrael) who were publicly voted in to become the Treasurers. This a multi-signature wallet with a 2/4 signing formula, so it needs at least 2 of the Treasurers to sign the spending transaction for it to become commutable. All spendings are published in the #devfund channel and are performed according to the results of public votes in either #funding-pools or #votes channels on Discord.

Kaspa was added to https://www.coinex.com/exchange/KAS-USDT Investors/traders welcome.
Team said the exchange was humble to list the project for free.

So I've tried to install Kdx on a couple computers... for a regular wallet I just run it as "node" right? when I try to create a "new wallet" I create a good password and when I click next it gives me the "password must be 8 characters... etc" warning???? yes the password fits all the criteria lol I can not wrap my head around why it's not letting me create a wallet 

Hummm did you get it to work?  :)

Not yet I was about to ask on their discord, do you have any hints? Ha I feel like I'm missing something very obvious lol

You need to launch the node, then you need to run the wallet, then run the 3rd CMD and use the wallet app with it's commands. Or use the online wallet, I forgot what was the link for that 1.

Best to ask on ther discord if you're still having problems. 
After you get your password problem fixed.... be patient because it takes awhile to sync.  :)

I thought that was just on the command line wallet not the Kdx wallet? or is that the mistake I'm making? lol

Sync time isn't too long after all there is a year of blocks to download

Interesting performance from this coin. Why is that? Can someone fill me in? A milestone is coming up or something, which causes this hype?

Looks like next x100 coin
also I notice in the community there is some kind of beef with Kadena, wonder why is that??

https://kaspa.org/     :)

look at the coin supply distribution after 1 year of mining, about as decentralized as I've ever seen a coin. plus the potential of "rust" protocol!!  :o

What is the rust protocol?  :)

They are rewriting the code from Go to Rust. This rewrite will substantially boost Kaspa's performance. Conservatively by around 10x.

https://twitter.com/MichaelSuttonIL/status/1593580087424712704

Thx Now I understand.  :)

New proposal for the consensus protocol for Kaspa:

https://twitter.com/hashdag/status/1598067571026075648

Ledger support coming for Kaspa  ;D

how to mine with amd card?

https://github.com/Lolliedieb/lolMiner-releases/releases

https://kaspa.herominers.com/#how-to-mine-kaspa-kas

Yes I figured it out... I had a "(" in my password, the warning didn't mention specific symbols you could or couldn't use in the password

Rust upgrade coming out April 15th. Potentially making the system 32x faster.

Rust mainnet went live April 16th. Uphold listing coming too.

no point mining now. china owns the chain with the (not released until August '23) 8.3Th/s ASIC miner.

Diff is 1.1P! Gone are the 95k days. 

Everyone can go home now... Was a nice ride. (Should edit the title, remove GPU and replace with ASIC)

I'm still mining with GPU'S  :)

Too early, asics crushed this coin under themselves. Now you can not dream of a multiple increase in the market rate.

Read the whitepaper, ASICS were planned day 1, so what's the surprise now?

I expected ASICs to come later and not be as powerful.

Yeah I didn't expect them to be this powerful as well, but c'on, we had 2 years till ASICs, so stuff is moving as predicted with this project.

Kaspa has now been listed on StealthEX

"StealthEX is a custody-free crypto exchange. We provide the opportunity to convert over 700 cryptocurrency assets limitlessly, without having to register, and with no extra or hidden fees. You can also buy a vast range of crypto coins using fiat currency"

List of Kaspa exchanges:
💰   Exchanges   💰
----------------------------------
 KuCoin https://kucoin.com/
 Gate https://www.gate.io/
 Bitget https://www.bitget.com/
 Uphold https://uphold.com/
 LBank https://lbank.com
 MEXC https://mexc.com/
 CoinEx https://www.coinex.com/
 Txbit https://txbit.io/
 Chainge (DEX) https://www.chainge.finance/
 TradeOgre https://www.tradeogre.com
 

The first batch of the IceRiver KS0 ASIC miners have been shipped with some already confirming delivery.

ICERIVER KS0 Specs:

 Description
KAS Hashrate    

100GH/S(±10%)
Wall Power    

65W/h(±10%)
Specifications    

100GH 65W
Dimension    

200x194x74(mm)
Net Weight    

2.5kg
Connection    

ethernet
Voltage Input    

With PSU:100-240V AC
Without PSU:19-20V DC
Operating Temp    

0~35 ℃ (Place in an environment with good air circulation)

https://hackernoon.com/the-power-of-kaspa-blockdags-go-beyond-the-blockchain/

Kaspa has now been listed on a new exchange

simpleswap.io


What is SimpleSwap?

"SimpleSwap is a user-friendly and reliable service for cryptocurrency exchanges. Our platform is free from sign-up and supports more than 500 crypto and fiat currencies"

Anybody can confirm that this is real?

https://www.youtube.com/watch?v=efWzZsUp744
KS1

He also has the KS0. :)

Kaspa has now been listed on a new exchange

https://www.rocketx.exchange/


What is RocketX?

"An advanced CEX & DEX aggregator to access 300+ DEXs, 6 Top CEXs, 20+ Bridges, and 200+ Networks"

Kaspa has now been integrated into NOWpayments.io

"NOWPayments is the best service that allows everyone to accept crypto payments on their websites, online stores, and social media accounts. It’s a non-custodial service, meaning it doesn’t hold or store your funds in any way. NOWPayments supports more than 50 cryptocurrencies, and it offers low transaction fees"

Rebuild AresMultiMiner support now KASPA coin.
Now fee - 0.5% for all algos
Support NVIDIA/AMD cards, also available dual mining.
Support "anti-overheat" system for your video cards
You can try - https://github.com/MultiMinerAres/AresminerRebuild

How does the "anti-overheat" system work? :)
This idiot does not know that the KASPA coin has not been profitable to mine on video cards for a long time due to the large number of different ASICs that are hundreds or thousands of times more efficient than video cards.

Why reinvent the wheel if it has already been invented?
Answer: to slip something else along with it. In this case, an attempt to slip a virus.

Why bother trying to mine when Bitmain is 'testing' their latest creation and earning 80% of all blocks?
Such scams coming from them.
Release? (possibly) August 2023, though still not a firm ship date.

Everyone should dump this coin now because only 1 company is mining everything.

Most of asics are on solo nodes and most of them are Iceriver asics that are already for sale to everyone.

kaspa pump to sell ASICs, watch and learn newbs LOL  :P

Shortly after you wrote that comment KAS corrected 30% and then went back up to make an all time high. Maybe you should do some more research on Kaspa and see how revolutionary it is as opposed to thinking this is another speed mine scam. There's a good reason it went up 300x during a bear market.

When Kas was idling at 2 cents, fudders said asics are coming it's time to dump and buy back at 0.005, a week later Kas did 2x up.

Only bad thing I have heard people say about Kaspa is they dont have any. Ledger also anounced support is coming soon. 

price is low today lol did will recover again. after all ROI si become longer.

"GPU PoW" .... Right..... Definitely

and ride on the coat tails of bitcoin and memes

Dont think Kaspa is riding anyones coat tails. I would say this video proves what Kaspa is all about.   https://youtu.be/9v5h3PK04JQ?si=0YhBGCm-8WOWbAeR

I consider Kaspa an interesting coin. :)

I'm maintaining various lists of "decentralized" coins in several subforums. I would like to add Kaspa to these lists but I have still some questions.

The most important requirement to enter the list is that there is no premine (nor any kind of mandatory developer fee). I consider everything as "premine" which is done either in the genesis block itself (as in most ICO/PoS/PBFT coins) or happens before the coin is publicly announced* by the developer(s).

According to early posts in this thread, there were three phases during launch of Kaspa:

- Testnet (before November 2021)
- "Gamenet" (November 2021 to somewhen in 2022), where coins were already valid for Mainnet, so it's basically already part of Mainnet.
- Mainnet (from 2022 on)

1) Was the testnet publicly announced*?
2) If not, are testnet coins valid in mainnet, or could they be exchanged for mainnet coins?
3) Was Gamenet publicly announced* from the start? Where - only in the Discord group or elsewhere?
4) If Gamenet was only announced in the Discord group, was the Discord group publicly announced* somwhere else before the start of Gamenet? (The OP of this thread stated that Gamenet had already started when the first post of this thread was made)
5) Is there any archived instance of the genesis block and the first blocks after them? (According to the first posts here Kaspa uses pruning, that's why I ask)
6) Is there a public chart of the mined coins since genesis?

If all the points are answered in a manner that proves there was no premine, I'll be happy to add Kaspa to my lists :) Of course, if they were already answered anywhere I'm grateful for any links.

---

*"publicly announced" for me means in any public forum or community, it isn't necessary that it was at Bitcointalk.

Hey you’ve asked a lot of questions many of which are answered on the KAS wiki FAQ page https://wiki.kaspa.org/en/faq . I have followed KAS since the early days and was one of the first discord members of the project. I know the project was mentioned in cpu mining forums back in the early days but I came to recognize it from a 2017 coindesk article that mentioned the founders work and DagLabs. By following the work of DagLabs I was led to the eventual discord channel and maintenance launch. In the early days the devs were solely focused on deving (they still are) but at that time there was almost zero marketing and only a few post here and there about the project. Anyway check the faq I posted and if you require a more nuanced answer on any particular topic after doing your due diligence feel free to ask again.

Thank you. I've looked into the FAQ. While it doesn't answer any of my questions directly, I guess from the code linked in the Twitter post about the genesis (https://twitter.com/DesheShai/status/1687201025344540672) block (https://archive.is/CxfVE) I can deduce that mainnet/gamenet and testnet were separate networks/coins, while Gamenet seems to be the "pre-deflationary phase" mentioned in the FAQ. However, it's a bit strange that the author of the Twitter post mentions a line in the "SIMNET" genesis block (which is normally a kind of testnet) to "prove" there was no premine, while the mainnet genesis block contains a quite big Coinbase section and also a non-empty "utxo commitment" section (line 77). It would be nice if somebody could clarify that :)

The thread's OP was written several days after Nov. 07 (the "gamenet"/mainnet launch). Thus, it would help the credibility of the coin's fair launch if links to announcements of Gamenet from prior to Nov 07, 2021 were published somewhere; of course ideally archived links (Internet archive, etc.).

Anyway, the info until now lets me believe that the start wasn't as fair as in Bitcoin or some very selected altcoins, but more in an "instamine" fashion, like in the case of Dash or Monero. This means that the team wasn't very eager to announce the launch. Which is of course understandable from an economic perspective. ;D

This does not mean that the coin has bad chances to be added to my list. I explicitly have added coins like Dash, because the "fair launch" question isn't black or white for me, and even BTC and LTC had few miners at the start, or some dominant miners (Charlie Lee in the case of LTC, Satoshi and Hal on BTC). The "red line" for me is a genesis premine or mining before the first public announcement (e.g. Bytecoin), so this would not affect Kaspa if the genesis block is clean and Gamenet was announced somewhere publicly, outside of Discord.

But it would be cool if someone could answer the question I raised above about the genesis block, and my questions 3, 4 and 6 from the last post :)

Someone else can answer the more technical questions, as to how people found out about Kaspa before it was mentioned on bitcointalk.

There were a lot of academic papers / stuff written by the creators which referenced Kaspa. I assume academics who were following the space, read his whitepapers/ tweets, and were interested to learn more found out that way:


About Kaspa (https://someone235.medium.com/scaling-bitcoin-with-blockdag-d785174a3402) This was back in April 26, 2021. There was a link to the discord at the bottom.  

Yonatan tweet about Kaspa in April 12, 2021 (https://twitter.com/hashdag/status/1381633444078309383)

Kaspa Github (https://twitter.com/hashdag/status/1395468577579356168) May 20, 2021

For #6: https://kaspa.org/wp-content/uploads/2022/09/KASPA-EMISSION-SCHEDULE.pdf

Thanks. I think these links answer all my original questions, as from the schedule it should be also clear that the first coins valid today were the Gamenet coins. While the oldest archived version of the Medium article is from December 2021 (and thus after the thread start), I give you the benefit of the doubt that the article wasn't altered between April and December. :) A Medium blog post in combination with a Tweet is "public" enough for me.

What's missing still is the explanation of the genesis block issue - if this is solved, Kaspa will be included in my list.

I may be missing something but can you clarify what your exact issue is regarding the authentication of the KAS genesis block? https://x.com/DesheShai/status/1691752128040059282?s=20 You should be able to follow the steps mentioned here and on GitHub to validate all blocks to KAS genesis point. 

I hadn't seen this guide, thanks. Will try to replicate the steps.

The issue was that in the tweet linked in the wiki FAQ (https://twitter.com/DesheShai/status/1687201025344540672) about genesis block integrity, the author referenced a line which is inside the code for the Simnet genesis block, to prove that there was no premine. In Bitcoin, Simnet is a testnet whose purpose is to get a completely private network with very low difficulty (https://gist.github.com/davecgh/2992ed85d41307e794f6).

If a Simnet line is used to prove that there was no premine, this looks at least a bit doubtful, so in my opinion if this was an error you should change it in your wiki FAQ. In my decentralized coins list (https://www.coingecko.com/en/portfolios/public/BAh7BjoRcG9ydGZvbGlvX2lkaQNkIME=--c49faeabf158a91fdf86303d67a8165a75dd2f72), Kaspa is at #5 (behind Bitcoin, Dogecoin, Litecoin and Monero) so I'm a bit more rigourous when investigating if it meets the "no premine" criteria than if it was a low-cap coin at #2000 or so, so if there is such a doubt, I ask :)

I guess that the block described as genesis in the code (line 66 ff of genesis.rs (https://github.com/kaspanet/rusty-kaspa/blob/ce3e231d0ae103557dc4c44a4dcf31265961a2e4/consensus/core/src/config/genesis.rs#L66)) is then the "hardwired" genesis block, i.e. the "checkpoint" which was inserted to repair the network split in late November '21, and that's the reason why its utxo commitment field isn't empty?

You’re correct in your assumption. It’s refreshing to have someone genuinely curious about the project and willing to take the time to actually research. If anymore questions arise feel free to ask and I’ll do my best to help answer or point you in the right direction.

You should join the Discord. All the important info is discussed there and people can answer more of your questions.

Kaspa ranking fixed on Coinmarketcap. Nearing 0.1$, Life is good!

I don't like Discord, I consider it a service which is very uncomfortable to use, above all to talk about technical issues.

But for now you both have answered the questions I needed. I've added Kaspa to the candidates for my next issue of the decentralized coin list. When I've time I will try to follow the steps in the guide you linked to create finally the proof for the fair launch.

Cat is out of the bag now. Kaspa is no longer a hidden gem coin. It is a blue chip coin now on its way to top 10.

Just my opinion, KASPA will reach a ranking of #3.  :)

is KASPA going to be just POW like BTC ffor the rest of its life and not going to turn into a L1 project sometime in the future?

it looks like it grew so fast already and us in the crypto community are not even aware of this project coming out live. i only notice this when its not $0.14 and it is already up on the 27th on CMC. i'm seeing hash will continue to grow. this isn't an ASIC resistant?

Kas is a layer 1 PoW chain like BTC. No the chain has never been asic or fpga resistant, in fact the end goal of chain security was always asics as stated in the whitepaper.
2 values that set kas apart of BTC, 1 second block times (10 blocks soon!) and aggressive tokenomics. Kas has 5.65% emission drop each month, no halvings.

more liquidity and then more exchanges.... then dump LOL  ;D  ;D  ;D


...let the newbs(bag holders) talk about the tech during bear market until the next market cycle LOLOL!

Well with Kaspa now on the Binance exchange for perpetual trading there has been some very big gains. It was added to Coinbase and saw big gains and now it is up 63% just in the last week with Binance.

https://crypto.news/kaspa-price-jumps-15-following-binance-listing/

I don't see it on coinbase. Do you have a link to the listing pair? thx  :)

Use uphold, they don't charge anything outside of kas actual network fee to move the coins in and out.

Hopefully it does and the dev should in no way think of migrating it from PoW to PoS. And this is the reason why it has gained its popularity because after Ethereum got out of PoW. Most of the miners have looked for continuation to mine and they've found it with Kaspa.

That's true, well, we will know it by then when the hash gets higher together with the difficulty. That's always the case with such rising stars in PoW scene. They are adapting to the situation.

Watch out here when you downloading the wallet

Looks very suspicious all , and a lot things going when you start the wallet.

Source: https://www.virustotal.com/gui/file/44eb8b9856eecc872c2ba6b88163dc567c2f2d72244887d878977637e2da3263/behavior (https://www.virustotal.com/gui/file/44eb8b9856eecc872c2ba6b88163dc567c2f2d72244887d878977637e2da3263/behavior)

well done~ ;D

That is the Electrum kaspa wallet. Virus total gives the official kaspa desktop wallet a clean bill of health.
https://github.com/kaspanet/kaspad/releases

https://www.virustotal.com/gui/file/59dce2aefefa67d3aaec863bae149c029fa95abb9db980568c5948d2bdfd074a

When mining cost is too much, they will jump on a new star. Smaller guys I mean, then next legend starts. So what's the glass ceiling an interesting question, some people feel they missed out, but it to expensive now for them to buy meaningful bag..... for pennies... Those times are over, a big strain on the "get rich" dream.

Kraken and Binance listed futures. I think spot is only a matter of time.

Be careful never to download Kaspa wallets that are not clear this is suspicious that there is a virus in the wallet.

Two people have spread this virus on the forum, I hope mods ban it soon.

Looks like bitcointalk have lost a lot of active members, just 12 pages for such an unique gem in more than two years.

just wanna say this.

the ship already sailed, just find another new shitcoin where you all can get in early hehehe

LEDGER integration is complete! Ledger Live still incoming
We can store our Kaspa on Nano S, Nano S+ and Nano X!

https://youtu.be/qCMFtagUftA

Kaspa is now listed on Changelly! 🚀

Based on the GHOSTDAG protocol, @KaspaCurrency is a proof-of-work #cryptocurrency that is fully scalable, open-source, and decentralized. Powered by $KAS.

Exchange $KAS ➡️ changelly.page.link/exchange-kas

I don’t know if this is a good place to ask, but currently looking for some advice about the best way to store kas cold, preferably with key offline…what’s the best way to keep it locked away? Any rec is appreciated. Thank u.

Tangem wallet or even Ledger that now supports Kas.

How is the security with those? Since they are connected to the internet, what are they risks of hacking, of getting compromised? Was looking for a method that would keep it all offline, but guess would be ok otherwise if security was very high.

Think the passphrase is stored offline.

I'am Casper. A_Ghost_Speedster 👻

Kaspa is now listed on Indian based exchange WazirX

India imposed a 30% tax on crypto gains back in 2022. Don't forget to pay the taxman!
 :P :D

Looks like smart contracts is well underway for Kaspa. Im done with anything ethereum related and solana could not carry the ball across the goal line when they had their chance this year. Hopefull Kaspa will be different.

https://twitter.com/kasplex/status/1782282685190414442

We are excited to announce the first stable #RustyKaspa (RK) node Release (version 0.14.1).

This is a significant milestone for the Kaspa network, as it marks the point where we shift to a new improved and optimized engine, which can now be built upon and accelerated to its limits.

https://medium.com/@michaelsuttonil/kaspa-on-rust-first-stable-release-636938596441