Topic: [ANN] SPECTRE (SPR) - ghostDAG - blockDAG - AstroBWTv3 - CPU-only-PoW - page 2. (Read 2866 times)

Time to fill the bags!

Only CPU now.

is there any gpu miner ?

Nethash increases everyday, but price

As far as I know, ring signatures were there from the very launch, https://bitcointalksearch.org/topic/xmr-monero-a-secure-private-untraceable-cryptocurrency-583449 . I don't know about hiding the amounts.

Anonymity have been the plan for XMR also.

Well if you've not seen the amount of Kaspa clone scams that's happened within the last 3 months, you're not in the know.

It is not anonymous at all, it offers no privacy features. Anonymity is their plan for the future. The price pumps now, though. Make of it what you will.

Sure, maybe its same dev as bitconnect, and maybe its satoshi too.

If only corelation is using a coin to be forked, then its all scam anyway

lol

Oh wow another Kaspa fork, same explorer, same DAG, same premine and ooohh same exchange listings. Wonder if its the same team behind the NXL and NTL pump and dump scams. Expect the website and explorer to disappear in 2 months.

would be great having xeggex/tradeogre

So, since Kaspa is now on Rust, Spectre is now on Rust?

Hmm.  Weird how that one works out.

Transitioning to the Rust Node 🚀
We're excited to announce a major upgrade for the Spectre Network: transitioning to the Rust-based implementation of the Spectre full-node. This change is crucial for the future of Spectre, addressing the limitations of the current Go node. The Rust node ensures better performance and long-term stability.

Spectre On Rust
Welcome to the Rust-based implementation of the Spectre full-node and its ancillary libraries. This node release is a drop-in replacement for the established Golang node and is now the recommended node software for the Spectre network. It introduces developers to the possibilities of Rust within the Spectre network's context, offering enhanced performance and reliability.

Your feedback, contributions, and issue reports will be integral to evolving this codebase and ensuring its maturity as a reliable node in the Spectre network.

Download the latest Binaries from here:
<https://github.com/spectre-project/rusty-spectre/releases>

Run the node:
spectred --utxoindex

If you appreciate our efforts and would like to support the Spectre development, please consider making a donation to the devfund 👇, managed by the Spectre community.

spectre:qrxf48dgrdkjxllxczek3uweuldtan9nanzjsavk0ak9ynwn0zsayjjh7upez


Spectre Golang
Effectively from now on the Spectre Golang node is deprecated and will neither get any further updates nor downloadable `datadir2` updates. With the switch to Spectre on Rust, users are no longer required to download anything manually. The header validation with our `rusty-spectrex` algorithm library has been improved significantly allowing ordinary users to sync from scratch. The Golang repository will become read-only and archived in GitHub.

Thank you for your continued support!

Looks promissing, I will buy some.

Thank you for your questions. Here's an overview of our development process and future plans:

We understand the community's eagerness to see the progress of our Rust full-node daemon. We plan to publish the repository once we reach a certain milestone that guarantees a stable and functional base. When it's public, this link will work: https://github.com/spectre-project/rusty-spectre

For those who might have seen it already. We've uploaded already a datadir from the working Spectre on Rust node to the downloads folder on our website at:
https://spectre-network.org/downloads/datadir-rust.zip.
You cannot use it right now, but it is from an already running internal `rusty-spectre` version using `rusty-spectrex`. Please don't use it with the Golang node.

Switching the UTXO model to the privacy one will require a hardfork and we plan to implement the GhostFACE protocol in Q4 2024 which will include advanced cryptographic techniques like Pedersen Commitments and ElGamal signatures for full privacy and anonymous transactions. You can find more details on our roadmap on our website and whitepaper.

- https://spectre-network.org/
- https://spectre-network.org/docs/Spectre-Network-Whitepaper.pdf

Launching the blockchain early, even with some features missing, helps build a community, gather feedback, test in real-world conditions, attract investors, and establish a strong market presence. People have different opinions on this approach.

Why don't you publish in Github what you already have of your Rust full-node daemon? Are Pedersen commitments hiding the amounts going to be implemented in the first release
of the rusty full node? Decent privacy coins such as Wownero, https://bitcointalksearch.org/topic/ann-wownero-such-privacy-many-coins-wow-3088712 , were already providing their users with the necessary privacy at their lauch. More than a month has passed since the launch of SPR and one can still see the amount out in the open displayed in the block explorer.
Do you consider desireable introducing pool-resistant solo mining in SPECTRE? Wownero already does it.

Announcement from Spectre Project!📌

We are thrilled to announce the release of two significant updates from the Spectre Project!

-----------------------------------------------------

SpectreX: Versatile CPU Mining Algorithm Library ⚡

We are excited to introduce SpectreX, a versatile CPU mining algorithm library, which will soon be integrated with our Rust full-node daemon.

What is SpectreX?
SpectreX features the AstroBWTv3 algorithm, a proof-of-work (PoW) system based on the Burrows-Wheeler transform (BWT). This is the world’s first implementation of AstroBWTv3 entirely written in Rust, without any external C dependencies. It relies solely on various Rust crates, offering a fully native Rust solution.

Improvements and Optimizations
The old version of the algorithm used a method called SA-IS for sorting. We improved it with SACA-K, but it could only use one CPU core at a time. Now, we use pSACAK, a new method that can use multiple CPU cores simultaneously, making it faster and more efficient.

There are still many ways to make the AstroBWTv3 method even better, such as:

- Replacing most steps with highly optimized inline assembler code on CPU.
- Partitioning the Suffix Array and offloading sorting to GPUs to significantly boost performance.

We encourage developers to optimize individual calculation steps to evolve the algorithm over time and mature the codebase.
Thank you for being a part of our community and supporting the Spectre Project.

For more information, visit:
https://github.com/spectre-project/rusty-spectrex
https://crates.io/crates/spectrex

-----------------------------------------------------

SpectreX Rust Miner: CPU Miner 🚀

We are also excited to introduce the SpectreX Rust Miner, a high-performance CPU miner for mining Spectre.

Features:

- Supports Linux, Windows, and macOS.
- Easy installation from binaries or source.
- Compatible with both Golang node and upcoming **Spectre on Rust**.

Quick Start Guide:

1. Download pre-compiled binaries from our GitHub release page.
2. Run the following to start mining: `./spectre-miner --mining-address spectre:XXXXX`

Please note that it is the reference implementation to demonstrate the Rust version of SpectreX with AstroBWTv3. Every mining software developer is invited to improve the performance of the miner and the algorithm library!

For detailed instructions, visit our GitHub repository at: https://github.com/spectre-project/spectre-miner

-----------------------------------------------------

Thank you for your continued support and being a part of the Spectre community!

For the miner to work, make sure your node is running and fully synchronized.

Exiting: Fatal error in goroutine `MAIN`: timeout expired
route 'rpc client - incoming' got timeout after 30s


I can `t connect...

2024-06-10 22:08:01.211 [INF] SXMN: Version 0.3.14
2024-06-10 22:08:06.225 [CRT] SXMN: Exiting: Fatal error in goroutine `MAIN`: context deadline exceeded
error connecting to localhost:18110
github.com/spectre-project/spectred/infrastructure/network/rpcclient/grpcclient.Connect
        /home/runner/work/spectred/spectred/infrastructure/network/rpcclient/grpcclient/grpcclient.go:43
github.com/spectre-project/spectred/infrastructure/network/rpcclient.(*RPCClient).connect
        /home/runner/work/spectred/spectred/infrastructure/network/rpcclient/rpcclient.go:47
github.com/spectre-project/spectred/infrastructure/network/rpcclient.NewRPCClient
        /home/runner/work/spectred/spectred/infrastructure/network/rpcclient/rpcclient.go:38
main.(*minerClient).connect
        /home/runner/work/spectred/spectred/cmd/spectreminer/client.go:26
main.newMinerClient
        /home/runner/work/spectred/spectred/cmd/spectreminer/client.go:55
main.main
        /home/runner/work/spectred/spectred/cmd/spectreminer/main.go:38
runtime.main
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/proc.go:267
runtime.goexit
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/asm_amd64.s:1650
error connecting to address localhost:18110
github.com/spectre-project/spectred/infrastructure/network/rpcclient.(*RPCClient).connect
        /home/runner/work/spectred/spectred/infrastructure/network/rpcclient/rpcclient.go:49
github.com/spectre-project/spectred/infrastructure/network/rpcclient.NewRPCClient
        /home/runner/work/spectred/spectred/infrastructure/network/rpcclient/rpcclient.go:38
main.(*minerClient).connect
        /home/runner/work/spectred/spectred/cmd/spectreminer/client.go:26
main.newMinerClient
        /home/runner/work/spectred/spectred/cmd/spectreminer/client.go:55
main.main
        /home/runner/work/spectred/spectred/cmd/spectreminer/main.go:38
runtime.main
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/proc.go:267
runtime.goexit
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/asm_amd64.s:1650
error connecting to the RPC server
main.main
        /home/runner/work/spectred/spectred/cmd/spectreminer/main.go:40
runtime.main
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/proc.go:267
runtime.goexit
        /opt/hostedtoolcache/go/1.21.9/x64/src/runtime/asm_amd64.s:1650
panic: Writing to the logger when it's not running

goroutine 40 [running]:
github.com/spectre-project/spectred/infrastructure/logger.(*Logger).printf(0x7ff63399efa0, 0x5, {0x7ff633b1788c, 0x4}, {0x7ff633b1d3b4, 0xb}, {0xc0000abfc0, 0x1, 0x1})
        /home/runner/work/spectred/spectred/infrastructure/logger/logs.go:185 +0x365
github.com/spectre-project/spectred/infrastructure/logger.(*Logger).Writef(...)
        /home/runner/work/spectred/spectred/infrastructure/logger/logs.go:144
github.com/spectre-project/spectred/infrastructure/logger.(*Logger).Criticalf(0xc000414000?, {0x7ff633b1d3b4?, 0x7ff634035668?}, {0xc0000abfc0?, 0x7ff634035644?, 0x0?})
        /home/runner/work/spectred/spectred/infrastructure/logger/logs.go:127 +0x4c
github.com/spectre-project/spectred/util/panics.exit.func1()
        /home/runner/work/spectred/spectred/util/panics/panics.go:58 +0xa6
created by github.com/spectre-project/spectred/util/panics.exit in goroutine 1
        /home/runner/work/spectred/spectred/util/panics/panics.go:57 +0x17c

Help me,no mining...