Trees are set in stone there is only a certain number of them. A single tree may have an unlimited number of branches. You can put a branch on your own tree and only on your own tree but this doesn't do you any good unless you maintain it as active which costs that account STAG to keep up. Even then, the benefit is minimal.

Depends on your definition. I came up with an alternate definition based on the root words. I will post a link to my explanation in a second.

Edit: https://nxtforum.org/alternate-cryptocurrencies/stag-qa/

Updated the post with a link.

Tonight I will be resetting Beta again. I will be including the full block explorer in the update. The other included improvent will be advanced transaction sorting. You may not notice this at all but it should prevent bots from front running the AE in the future.

Here is how it works. Transactions will be sorted first by a weight algorithm which factors in the timestamp and the transaction fee. Transactions with higher fees and lower timestamps will be added to blocks sooner than those with lower fees and higher timestamps. After that, they are sorted directly by fee; transactions with higher fees are more likely to make it than those with lower fees. After that, they are sorted by amountNQT; the larger the amount NQT, the more likely they are to get in. After that, they are sorted by how many bytes they contain; the more bytes, the more likely they are to get in. Finally, if everything else is equal, they are sorted by transaction ID in ascending order; the lower the transaction ID, the more likely they are to get in.

There are reasons for this explained on the NXT forum here: https://nxtforum.org/general/transaction-sorting-ideas-for-the-future!/

Thanks for your help. If you can try it with the api, I would appreciate it a TON.

I have made progress getting the blocks visible. I even made a little page search box so you can browse every block from the comfort of your client.

I would but I don't want to distribute demo versions of Stag to people I don't know just in case someone trys to distribute it before it is ready.

EDIT: Happy Thanks Giving to all my US friends!

This makes me uncomfortable considering the transactions are going through. If a double spending issue comes up, the transaction should NOT go through. Could someone please try sending more coins than they have back to me to see if the transaction still goes through?

And someone else try sending all their coins to another account and then try sending more in a separate transaction on the same block. I want to make sure REAL double spending transactions don't go through.

EDIT: I forgot to activate the account on the second brother tree so it has just been collecting inflationary block rewards with no brother rewards going to other accounts because its Brother Tree was completely inactive. I fixed it now so people should start receiving Brother Rewards. About 10 of them will happen before we even out the total Stag in the economy and the ideal stag in the economy.

Will be dumping a bunch of test Stag into an inactive account. This should cause Brother Rewards to be sent out (as Stag will enter a phase with new Stag being added to the system). I want to make sure other accounts are getting added to Brother Trees properly. If you recieve a BR, please tell me so I know it is working. You will know you have received one when your balance suddenly goes up but nothing is added to your Forged Balance. Thank you to all my testers!

1. I noticed this too. It happens after you send your first transaction per log in. You can get around it by refreshing the page and logging in again. I will work on fixing this as one of my top priorities.

2. Same type of thing as above. If you refresh and log in again, it fixes the issue.

That is a known issue with the public UI. The transaction does go through though. It will happen with every transaction you make.

added a buy order and a sell order. Seems like it is working so far.

Building a crypto (even a fork of an existing crypto) is not easy if you you are going to do it right. I basically work full time on it because it is very important to me that I do this right.

---

I have reset the server with an update. It should now be able to function for a large number of blocks without crashing. I have also sent out test Stag for everyone to play with again.

I issued a test asset as well. I would like all beta testers to buy and sell some of it with their test coins to make sure the Asset Exchange functions properly. It will go through at block 2. When it does, will post the Asset Id and Issuer Id below so you can find it. Feel free to issue new assets to test as well.

Asset ID: 5483821208322915655
Issuer Id: STAG-K96U-N3NP-4ZWG-4R7YT

It is supposed to be in red on yours because that is STAG taken away from your account. It is green on mine because it is STAG added to my account. It doesn't mean there was an error.


That is normal when there are less than 10 blocks and we ARE technically on a fork of NXT; it is just a fork at block height zero.

If you want some to play around with, send me a PM with your account and your public key.

There was a crash on the node I linked you guys, too due to an error in the code which finds the Brother Reward recipient for the block. I will be updating it momentarily. I will try to save the DB but I might have to get rid of it which would mean sending all the test transactions over again which might take about 30 minutes. Thank you all for your patience!

Just send me a PM saying you are interested in initial distribution.


Odd, I received the coins back. Thank you for finding the first bug (well the first one I haven't found yet).

Sorry, I forgot to change a setting in the config file. It should be working now and all coins should be sent out.

You just have bad timing. I was just doing a quick update which hopefully fixes the 31 block bug.

Good point. Or put it in a pm.

I found a bug which causes Stag to crash once 31 blocks have been forged. Until this is fixed, Stag will be periodically reset and funds will be resent to testers.

This bug has something to do with too many database connections being opened (I think). I am taking today off but will do my best to fix it as quickly as possible.

Thank you all for your understanding and support.

OPEN BETA IS HERE!

Stag open beta is here! I have a public node with an open UI as well as a public node with a closed UI for it to exchange data with. So far, they have been sufficiently exchanging blocks and transactions with each-other so I am opening up the beta testing phase for public use.

What to do!
Go to the URL listed in the "Where to go" section and create an account. Write down your password somewhere or save it to your computer. There is no need to worry about security as this is only beta and upon official release, all coins from beta WILL DISAPPEAR! Once you log in for the first time, you will be given a public key. Post your public key here along with the amount of STAG you want to use for testing. I will then send you some STAG using your public key! After that, play around and goof off! If you find a bug, please post it here!

What NOT to do!
Don't use the password you used for beta for a real account when Stag is finally released as the server is set up for debugging and I WILL see the passwords you used in beta! So please, don't tempt me by using a password you used for something else or using the same password for beta as you do for the initial release!

Also, don't report typos (yet)! This includes instances where something says "NXT" instead of "STAG." I will get to these later.

What to expect!
Likely the biggest existing bug is the fact that when you try to make a transaction, you will see an error stating "Could not verify signature (Server Side)." Despite the error, the transaction IS excepted and will go through in the next block. This has something to do with the fact that you are logging in remotely (i.e. you are logging into Stag through something other than localhost). I am aware of this bug and will fix it, but it is not my highest priority as every day use of Stag will be done through localhost.

Where to go!
To help with Beta Testing, go here: http://104.131.29.158:7826