KevaCoin by Community

[d47081]

As there is no updates for this repository for a long time, here is alternative branch by community:

https://github.com/kvazar-network/kevacoin/tree/kvazar

It includes following updates:

• https://github.com/kevacoin-project/kevacoin/pull/39
• https://github.com/kevacoin-project/kevacoin/pull/38
• https://github.com/kevacoin-project/kevacoin/pull/36
• https://github.com/kevacoin-project/kevacoin/pull/35
• https://github.com/kevacoin-project/kevacoin/pull/34

Some builds for Linux also available on Releases page:

https://github.com/kvazar-network/kevacoin/releases

Visit also:

• KevaCoin Thread on BitcoinTalk
• Some community at Discord

If you can't connect the network, use alternative DNS:

• kex.keva.one - probably port 50002
• [201:23b4:991a:634d:8359:4521:5576:15b7]:9338 - Yggdrasil peer by YGGverse

Active mining pools:

• https://miningpoolstats.stream/kevacoin

Active KevaCoin services:

• https://github.com/kvazar-network/awesome-kevacoin

Feel free to share your resources and join the development by community!

[344303947]

This is a fantastic start, and we're especially looking forward to this community's growth—eagerly anticipating more and more developers joining in to contribute socially.

[d47081]

I would like to see the activity here, but until that happened, let's do some updates as codebase dependent of OS updates.

Thanks to you, I have just found this project: https://github.com/keva-dev/keva

What is this in few words? Looks useful also

[canrnd]

Can see https://github.com/kevacoin-team for collaborative updates. Given activity here I have cleaned up repos so issues can be digested over there.

kex.keva.one is my electrumx host meant for supporting mobile wallets using keva_wallet, not proper seeder. Since desire exists I'll setup proper dns seeder on keva.one for inclusion.

Development focus on core chain been on reintegrations across various bitcoin versions; I will work on bringing this back in but on the latest so it can be completed. Some the public work on older version can be seen in archived repo.

[d47081]

@canrnd kevacoin-team is your project?

let me know about seed update or just make PR here to include all the upstreams: https://github.com/kvazar-network/kevacoin/tree/add-kex-keva-one-dns

btw, this branch is main, already includes lot of updates, including last PRs: https://github.com/kvazar-network/kevacoin/tree/kvazar

so you can use updates from there for your project.

please share the software you are using for seed, maybe I'll launch it too, even 53 port already in use.

[canrnd]

kevacoin-team more or less the community. Kevacoin and I are joint admins of the the orig and its repos. Admittedly outside breaking bugs I've spent my time on https://github.com/kevaone/narwhallet which is centered around the kevacoin chain.

Process undetermined on seed at the moment, just bumped the goal in the list so need to look into compliant way to setup but can share once solved.

With landscapes changing and interests gaining the team org going to get more attention. With focus on new client (no change in chain except ability to active/deactivate new features like taproot). Newer client performs much nicer so everyone will get to benefit and opens up options for chain enhancement via enabling features.

[d47081]

Cool, added these resources to awesome-kevacoin registry.

So you have an access to accept PR in this repository? Because I found no activity about few years here, until created new branch.

If you have an access why not to just continue development here?

I wish to make another fork also, with larger values size and less block rewards: https://github.com/kvazar-network/kevacoin/issues/12

Change it in the current network have no sense, because of miners consensus.

[canrnd]

I can only work on pr within kevacoin-team and kevaone repos. kevacoin-project considered inert; the continuation for core chain and some starting framework are in kevacoin-team and moved as updates/changes require.

Correct, changing sizes and reward schedule would be fork and thusly a new coin.

I would consider halving upcoming so block rewards will be reduced down to 250 so rewards naturally getting reduced before long. Larger key sizes are often wanted to accommodate storage of files and/or their chunks. While doing this is possible its not recommended for all data, poor use of key value and burden of overall chain size can occur, esp over time. An option for larger content is utilizing kevacoin as source of truth with meta data and signatures and combining with a file based solution allowing for better choice of storing the larger content. IPFS is rather popular but there are many options tailored for files or blobish data.

[d47081]

With current block rewards there is no resistance for DoS, because huge data can be sent partially anyway.

Just though won't make new fork, and wish to keep current blockchain, maybe once mining will be closer to stop (hashvault just dropped this coin too).

imho, for metadata storage, enough less of value size, but in keva has not small for meta, not large for data values.

so I see following changes useful:

1. reduce reward
2. enlarge value / block size
3. probably, removing coins mining limit would be useful also, if this blockchain positioned as DB - no ideas why it's finitive
4. remove pseudo delete operations or at least implement local cleanup by that features (currently that's fake commands)

The idea you've mentioned about IPFS over blockchain - is not new, that's implemented in twister p2p. But with time I found that DHT data lost there. So I'm interested in storage in blockchain only where data placed as part of the network chain.

[canrnd]

1. Block rewards won't change and shouldn't as these are foundational values of the chain, coming up on first halving so mining rewards reduced anyway. If network begins to see abuse the first thing to do is hike fee's.
2. value and the block size in good place given the 2min target interval. aside from it being more resistant to file archival the blocks are able to traverse across the network at fast enough rate chain not always fighting for top.
3. Not quite sure what you mean here?
4. Agree, some aspects odd and need better definition around where / how things are used. new client best place to work on fixes so will try and get future client up to state regtest can be ran and we can deal with things like this as new client gets pushed forward.

blockchain file storage hard ask unless network purpose built for the task. Maybe Filecoin if still around a better solution for raw file needs?

[d47081]

Increasing the values size currently limited by the block size. It's impossible to change the value without changing the block, because in current implementation increase may out of max size. Some details here:

What is the maximum block size?

3. Not quite sure what you mean here?

I meant that cryptocurrency model not adapted for data storage needs, it's mostly oriented to keeping currency rate. According to that, people will be interested in money holding as has limited quantity.

In my opinion, people would have as lot coins as they need to store the data, e.g. mining == storage. Always. But with time they will must to purchase this storage and nobody interested in that. It works just until it's free / mineble, imho

Some interesting implementation has Alfis DNS that works without coins, and provides storage for domain records as long as miners ready to mine.

Anyway, it's better to change nothing at the moment, this coin still optimal for microblogging, even I wish to keep larger articles sometimes. Just thought. Another thought is have unlimited value size at all, with related commission, just subject for another coin