Topic: [ANN] Stag! | Stagflation crypto based on NXT! | OPEN BETA (Down for testing)! - page 4. (Read 49381 times)

Same for me too

Failed to connect

http://104.131.29.158:7826

Oops, forgot about that in the big update. Fixed now. I also figured out what was going on with the nodes not connecting. I made a typo when adding their data to the database. It should be working well now.

Every action ends with "Could not verify signature (server side)".

And I forgot to change the peer requests in the blockchain processor so that new blocks don't go through. One more bug to fix today sigh.

you are doing a great job. Will check the new beta

It took some tweaking, but I finally got it working, there was an error processing peer transactions so the two nodes blacklisted each other. I fixed it now and spent most of my day doing something I said I wasn't going to do... That is, debugging the new version of Stag...

Great job Stag i pm you if you want again bêta tester.

---

The latest version of Stag Beta is now on the public node you guys are used to by now! This Version utilizes NXT 1.3.4 at its core and offers new features such as searching the marketplace for tags, description text, and title. It also has a slicker design.

It also offers a modified version of transaction sorting/execution that won't be included until NXT 1.4.0.

This method sorts unconfirmed transactions first in ascending order of height where new blocks have a height on Integer.MAX_VALUE and blocks that have been attached to a block and popped off have the height of the last block they were attached to. Next, they are sorted by TX fee per TX byte in descending order. Next they are sorted by a Bit value in descending order where the value is 1 if the transaction sender is logged into that node and 0 if they are not. After that, they are sorted in ascending order of their arrival timestamp. This is a marker indicating when the unconfirmed transaction arrived at the node forging the block. Next, they are sorted in descending order by the amount of NXT being transfered in the transaction because I am assuming that the more NXT that is transfered, the more important the transaction is. Finally, it defaults to sorting the blocks by transaction ID.

Transactions are executed and stored in the block by the arrival timestamp at the forger's node in ascending order, the height of the transaction in ascending order, and finally by transaction ID in ascending order.

As I mentioned before, I don't have time to look for bugs today so I am counting on all of you to do a good job for me!

This really looks promising! Good job dev.

I have some good news and some not so good news. The good news is that the new update is forging just fine and I will update the node tomorrow with the latest version. The not so good news is that is all I will be able to accomplish tomorrow as I have other obligations to attend to.

Ah. So I am inches away from being able to send out the new version. With it will be another blockchain reset. Hopefully I can send it out by tomorrow.

I said the old version.

That is weird, because I haven't sent out the update yet.

Great job Stag.I test again and it's ok !

You are doing a great job Stag regarding all the bugs we have been having, I will be looking forward to the full Release of STAG in due time and your ever growing support

Working on overhauling Stag with the latest version of NXT.

Just updated the post above. It is another issue related to the remote client.

Tried to register an alias, same message.

Hmmm, the could not verify signature server side is something I thought I fixed. Anyone else getting this error?

EDIT: I tested this on the local client and it worked fine. Must just be an issue with remote client access. Also, a minor announcement: I will be upgrading the UI to the latest NXT UI (mostly because it is nicer and allows you to search the marketplace easily). There will likely be new bugs after this update so be ready for a whole slew of new issues!