Bitcoin Forum

Hello Bitcointalk Community! I am thrilled to introduce you to apsaK (SAK), a new PoW meme coin that I have developed. It's a reversed fork of Kaspa, with a reversed kHeavyHash that is GPU friendly. This unique feature makes apsaK an exciting addition to the GPU-mining world and a fun meme coin in the crypto space.

* apsaK Specifications:
- Coin: SAK
- Algo: Reversed kHeavyHash
- Block Time: 1 second
- Pre-deflationary Block Reward: 50 SAK
- Post-deflationary Block Reward: 5 SAK
- Total Supply: 500,000,000 SAK

* Unique Features:
- Reversed kHeavyHash: No ASIC-miners, like in early Kaspa.
- Community-Oriented: No dev-fees in the consensus, making this a truly community-driven project.
- Transaction Fee and Burn Mechanism: I've implemented an increased transaction fee and a mechanism to burn 99% of transaction fees, reducing the total supply over time.

* Technology:
- Built on Rust.

Please note that the roadmap and whitepaper will be released later. For now, I am focusing on building a strong community and working closely with the community for further development.

I invite you to join me in this exciting journey. Let's make SAK the next big thing in the crypto world!

For more information:
- apsaK NG app https://apsak-ng.net
- Explorer https://rerolpxe.apsak.net
- follow me on Twitter https://x.com/apsak_org
- check out the GitHub https://github.com/apsaknet
- join our Discord community https://discord.gg/Fp76JwC5GS

Site, explorer, white paper?

I like it.

There are no issues in https://github.com/apsaknet/rusty-apsak and so let me ask here.
I get this when i try to compile the daemon with cargo build --release --bin apsakd:

   Compiling librocksdb-sys v0.11.0+8.1.1
error: failed to run custom build command for `librocksdb-sys v0.11.0+8.1.1`

Caused by:
  process didn't exit successfully: `/usr/local/src/rusty-apsak/target/release/build/librocksdb-sys-e6eb7496d5737ff3/build-script-build` (exit status: 101)
  --- stderr
  rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found
  thread 'main' panicked at /home/ap/.cargo/registry/src/index.crates.io-6f17d22bba15001f/librocksdb-sys-0.11.0+8.1.1/build.rs:40:10:
  unable to generate rocksdb bindings: ClangDiagnostic("rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found\n")
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace



RUST_BACKTRACE=full cargo build --release --bin apsakd gives a more verbose output:
   Compiling librocksdb-sys v0.11.0+8.1.1
error: failed to run custom build command for `librocksdb-sys v0.11.0+8.1.1`
note: To improve backtraces for build dependencies, set the CARGO_PROFILE_RELEASE_BUILD_OVERRIDE_DEBUG=true environment variable to enable debug information generation.

Caused by:
  process didn't exit successfully: `/usr/local/src/rusty-apsak/target/release/build/librocksdb-sys-e6eb7496d5737ff3/build-script-build` (exit status: 101)
  --- stderr
  rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found
  thread 'main' panicked at /home/ap/.cargo/registry/src/index.crates.io-6f17d22bba15001f/librocksdb-sys-0.11.0+8.1.1/build.rs:40:10:
  unable to generate rocksdb bindings: ClangDiagnostic("rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found\n")
  stack backtrace:
     0:     0x5dc54ab55722 - <unknown>
     1:     0x5dc54ab8093c - <unknown>
     2:     0x5dc54ab522cf - <unknown>
     3:     0x5dc54ab554f4 - <unknown>
     4:     0x5dc54ab56d1b - <unknown>
     5:     0x5dc54ab56a73 - <unknown>
     6:     0x5dc54ab571bd - <unknown>
     7:     0x5dc54ab57092 - <unknown>
     8:     0x5dc54ab55bf6 - <unknown>
     9:     0x5dc54ab56dc4 - <unknown>
    10:     0x5dc54a46b615 - <unknown>
    11:     0x5dc54a46bb03 - <unknown>
    12:     0x5dc54a46e940 - <unknown>
    13:     0x5dc54a471e3c - <unknown>
    14:     0x5dc54a475902 - <unknown>
    15:     0x5dc54a46d703 - <unknown>
    16:     0x5dc54a46c976 - <unknown>
    17:     0x5dc54a46d049 - <unknown>
    18:     0x5dc54ab4cd83 - <unknown>
    19:     0x5dc54a46d027 - <unknown>
    20:     0x5dc54a475ff5 - <unknown>
    21:     0x7cadbce29d90 - <unknown>
    22:     0x7cadbce29e40 - __libc_start_main
    23:     0x5dc54a46bcb5 - <unknown>
    24:                0x0 - <unknown>



I am on Ubuntu Desktop 22.04LTS

It's been 3 Days since Mainnet launched and you remember to post on Bitcointalk now? Unfair Launch !

and you wake up about it now it was posted 10 hours ago :D

There.. There...

Just curious? Do You have any evidence of that? I hope You have as claims without an evidence are called SPAM and FUD. Reported to moderators.

go mining if you want, but sell when they exchange. I know why i say that, in 3 month since the add in exchange go this post and say "sorry"

It is the same development style of both Kapsa Classic and k0bra dag, which were both forks and failed projects with devs selling premines.

 Also this coin is not fair launched and has a premine.

Do You have evidence instead of personal thoughts ? Show Us.

Same style of development :D many starting projects are developed in same style :D

Website and explorer are being developed, whitepaper is also not available yet.

I need more information for debugging, you can pm me on Discord and we can try to figure this out together

I get this when trying to GPU-mine with this command apsak-miner -a apsak:q********************************************************7  :

[2024-06-10T06:59:35Z INFO  apsak_miner] =================================================================================
[2024-06-10T06:59:35Z INFO  apsak_miner]                  apsaK-Miner GPU 0.2.1-GPU-0.7
[2024-06-10T06:59:35Z INFO  apsak_miner]  Mining for: apsak:q**********************************************************************7
[2024-06-10T06:59:35Z INFO  apsak_miner] =================================================================================
[2024-06-10T06:59:35Z INFO  apsak_miner] Found plugins: []
[2024-06-10T06:59:35Z INFO  apsak_miner] Plugins found 0 workers
[2024-06-10T06:59:35Z ERROR apsak_miner] No workers specified
Error: "No workers specified"


I have obscured the address for the privacy reasons.

make sure the files libapsakcuda.so and libapsakopencl.so are in the same directory

Initially, premining was not planned, everything turned out as it did. I believe it’s right if the community itself decides what to do with it.

you are mistaken in associating me with cas

I have compiled the miner from source myself but I am using apsakd included in the latest release. Can it be the reason? I moved them all to /opt.