Topic: [ANN][POW] 👾Torque👾 - decentralized node list via IPFS & ZeroNet - page 19. (Read 87266 times)

what is happening with communitypool? coins are not pay out... i have value x4 more than minimum pay out

coin will go to the moon soon enough

Roadmap Update (19 June)
https://coindar.org/en/event/stellite-xtl-roadmap-update-10849

Thank you... its working

load blockchaindownload and after its done startup only stellited.exe till full sync. close it then start wallet and connect to localhost daemon

i have the same problem.. can someone help please

good job!

Features:

- Mining to exchange

- Workers

- Adjustable instant payout levels

- Email and telegram notifications

- SSL

Hey Everyone,

We were working hard for the past few months to make some mandatory improvements to our network.
We successfully hardforked last week as we always did. We're happy so far with the results we had.
The new difficulty adjustment algorithm is performing even better than expected. We'll now focus again on the development of Stellite ecosystem.
The cornerstones of this ecosystem are :
- StellitePay (Subscriptions opened, invitations are coming)
- Smart Mobile Mining
- IPFS integration
- Mobile wallets
Lot of all this have been put aside for quite some time, as network improvements are always the top priority for a cryptocurrency project. You can't have nice things if you don't have a good network serving as a foundation.
Also we have big goals and a broad vision for our project, so building all these things while having some quality software takes time. You guys also know we love to test a lot what we're doing
On a side note, we're also working on having the code of our past fork reviewed by some renown people always in the idea of aiming for quality first (Zawy just reviewed our DAA and called it a "tough good algorithm").
A new awesome contributor (@artarf) recently joined and is working with us on a branding to more reflect all of this in our public image.
We are also always actively looking for contributors, so if you want to make all of these awesome things happen with us, you're welcome to come and talk to us, we'll guide you and help you (you don't need to be proficient in cryptonote protocol to join us, we need everything from design to webdev to highly low level C++ programming) we'll review every proposition you guys make and would warmly welcome you in the team. You can also contribute by convincing merchants to accept XTL as payment method, mining on small pools and spreading hashrate, and whatever your creativity allows you to do.

Kind Regards,

From the XTL Developers

Using the latest GUI wallet, daemon fails to start, prompting a window:


I set the daemon address nodes.stellite.cash and port 20189 then clicked connect and network status is synchronizing now but daemon doesnt start anyway.

Here is the daemon log:

Thx. With the new wallet (after manually choosing the external node because it's not set by default as described) the balance immediately shows up correctly. The daemon itself  still does not seem to sync correctly, so for now I will just stick to the external one.

Guys a new wallet Version is out. Just came out couple of hours ago. Maybe you should try that !

Same to me. From time to time the wallet is freezes, not syncing, and switches between synced and xxx blocks behind, as written in the quotation.

Just synced my GUI wallet (last version), no issue. I was 2K+ blocks behind. It took a few minutes.

Hash per second algo  Stellite V4=Stellite V7

Yep, there might be a problem with the latest build since tradeogre seems to have issues with it as well. Deposits are hit and miss, took half a day yesterday and the same thing today, the wallet has probably stuck, was restarted and now stuck again?

idk whats the problem. I sync until block 70k close the wallet. later the wallet starts syncing blocks from 175k blocks  I did try many times. it goes back 100k-something blocks

so hows the new algo steelitev4 like heavy or v7.
i setup soon my rig

edit:its cnv7 style

thnx

It seems like since the fork the daemon has some hickups. It often switches between "synced" and "xxx blocks behind" and I think the reason is, that there are still "old" nodes in the network.
Is there any way to either auto-ban nodes that are on a wrong version OR have the daemon start with a reliable up-to-date node in exclusive mode (maybe through something like --add-exclusive-node [IP])?