 Show Posts
|
|
Pages: [1] 2 3 4 5 »
|
I think the most important think is the open public blockchain this public ledger which makes everyting which is owned by the public transparent, so everyone can trust each other or don't have to trust each other anymore because they only have to have trust in the blockchain (DAO) Then people can start working together to solve problemes of the public. The nice thing is that because everyone can then contribute to the DAO by explaining their individuell tansions (problemes) and find people who have similar tansions to solve them together more quick. The blockchain has made the creation of money open for everyone. In a DAO the money of the DAO is the representation of the value of the DAO and the votingpower. Every time you buy something you vote. If you buy tokens for a DAO you vote for the DAO. It would be good if everyone tries to buy things which solves their tensions. What are tensions? Tensions a relative but people can have similar tensions. It is possible to solve tensions. There are lots of different tensions the only task is to solve proplemes as efficient as possible. Erveryone should focuse on those tensions which he or she has and find other people who have similare tansions to solve them. it is like a game. This DAO (kind of crowdfunding, social media plattform) has different rules, like every game, which says for example, that every Solution for the tension has to be good for the enviroment and the people or shouldn't harm the people and the enviroment. The purpose of this plattform is to connect people and support them with money, infrastructure, contacts etc.. Because this plattform is owned by those who solve proplemes which are good for the people and enviroment, because those people will get DAOtokens from other people to solve their common tensions (for example cleaning the beach, electric cars, education etc.) So the money (ownership of the DAO) will always go to those people who help the people and enviroment. The DAO Tokens have a fix ammount and a negative interest. The negative interest is there so people don't hold lage ammounts of money. People invest their money so they don't lose money. The money should be always in circulation. The higher the negative interest the higher the circulation speed of the money within the system. There hast to be a good balance between the negative interest rate for example 5% per year, similar to www.freico.in "Freicoin introduces the concept of a small holding fee, called demurrage, to virtual currencies. Currency owners automatically pay this fee. This promotes currency circulation and encourages sustainable investments. This fee, 5% per year, re-enters the economy through miners who use a large portion of it to pay for operating costs." Charles Hoskinson Tells Us Why He Is 100% ETC http://www.ethnews.com/charles-hoskinson-tells-us-why-he-is-100-etcFreicoin has a "Foundation". It means a group of control, like Ethereum. Not neutral. Money should be morally neutral, not good or bad, but neutral. And not controlled by any group. Run away from any coin with a "Foundation". |
|
|
|
Oooh!!, big news!, thanks to you, btc38, now there is a market for NAS again   I tested deposit and withdrawal, and it worked fine and fast (just a minimum of 200 NAS is needed for withdrawal). It was almost free because BTC38 bonus of 1% in deposits, which compensate for usual 1% in withdrawal. Also, a minimum of 0.001 BTC is required to trade (which is ~20000 NAS now). I also found a bug in Nas v. 1.1.6.N1: "Send NAS" doesn't work  As it was other suggestions of not proper working in Linux, I recommend to still use 1.1.3.N2 or 1.1.3.N1, until we can solve that problems in a new 1.1.6.N2. |
|
|
|
@patapato While i'm at it, there are a few little things wrong in the shell script "*.sh" files for Linux: - Line endings: the line ending in the script files is "CR LF"(\r\n)[windows line ending] and should be only "LF"(\n)[*nix line ending] - compile.sh needs also changes, here is what i'm using(should match win-compile.sh): CP=conf/:classes/:lib/*
SP=src/java/
/bin/mkdir -p classes/
javac -sourcepath ${SP} -classpath ${CP} -d classes/ src/java/nxt/*.java src/java/nxt/*/*.java || exit 1
/bin/rm -f nxt.jar
jar cf nxt.jar -C classes . || exit 1
/bin/rm -rf classes
echo "nxt.jar generated successfully"
Hi User1397367406, I would like to give you write access to the Bitbucket repository (except "master branch"), I already gave access to tiker. Then you could do those changes and upload a correct zip file made in Linux, deleting the current one. I tried to compile with Java version 7 compatibility from the IDE, but I forgot it at the end as I compiled with the script, which used my most recent version of Java. Line ending should be correct in the sources, as Git makes the conversion when commiting. The other change that you write is enclosing the variables 'SP' and 'CP' between brackets. If it is necessary I would make an "amend commit" in order that it will be correct in the sources as well. 'win-compile' is slightly different in that it needs quotation marks in 'CP' value. |
|
|
|
I try both 1.1.6 and 1.1.3 but get a error: Error: Could not find or load main class nxt.Nxt
The java is version 1.8.0_45 This can be a problem with these new versions of java? Which version are you running? Are you using the sources or the zip file?, Linux or Windows?, Maybe it's a problem of directory or files permission in Linux, as distribution file is zipped in Windows. That Java version is not the problem. |
|
|
|
Why do you think that the network isn't strong enough to continue updating NAS? Anyone who's running a node is either not watching this thread and still forked from the attack and going no where, or are watching this thread and will know that a new version will be coming out and will update.
If Bter hasn't fixed their node, it might be easier (less work) for them to just download the new client and download the chain cleanly from the network again. Otherwise they'll be wiping the client, downloading the data, bringing their node offline when the new version comes out, possibly download the chain again, etc.
There are some major bugs that are fixed with newer versions of the NXT client. I don't think that stopping the NAS patching at 1.1.6 leaving the rest of the bugs in place due to the fear of nodes not updating is a wise decision.
Well, maybe you are right. But the attack that we suffered was not because a bug, and we lost the only exchange that was available, Bter: "NAS deposit is disabled 因技术维护，虚拟币充值暂停，感谢您谅解和支持。" If we are going to update further, we need to decide and agree on a block height at which the new features will start working. After that, the current clients will not work. The WinNAS client will also not work with greater version updates (I know, nobody is using it, but it works  ) I would like to read more opinions, in favor or against. Do you, people, want NAS to be a full updated clone of NXT?, would it be an incentive for new users and exchanges?, are there any other ideas for the evolution of Nas?. |
|
|
|
NAS version 1.1.6.N1As I told before, once we got the sources of Nas for one version, it is easy to update to further versions of Nxt. So I updated the Nas Client sources to the last of 1.1.* series in Nxt, which is 1.1.6. Client download: Nas Client 1.1.6.N1Sources repository: https://bitbucket.org/patapato/nasThis is the last version which can be updated without modifying the blockchain database structure. The next version of Nxt was 1.2.0e, which introduced the new feature Digital Goods Store, needing to update de DB. It would mean that everybody would have to update their clients before a predetermined block height. But it would be dangerous for the weak Nas network, with few nodes working now, and it would be a mess for the exchanges, which has not even synchronized the blockchain now. Version 1.1.6.N1 is not dangerous, you can test it and go back to 1.1.3.N? whenever you want, as the blockchain structure is exactly the same (anyway, it is always recommended to do backup of the blockchain file before running a different version). Thanks to all the people who gave encouragement!.
|
|
|
|
Nas Coin creator, profile name Nas_Coin, is not dead. He renewed his domain, nascoin.org, 19 days ago, on April 5, after expiry date March 24. Surely he is following progress of Nas here. Domain Name:NASCOIN.ORG
Domain ID: D171574393-LROR
Creation Date: 2014-03-24T12:07:51Z
Updated Date: 2015-04-05T09:55:06Z
Registry Expiry Date: 2016-03-24T12:07:51Z
Sponsoring Registrar:GoDaddy.com, LLC (R91-LROR)
Sponsoring Registrar IANA ID: 146
WHOIS Server:
Referral URL:
Domain Status: clientDeleteProhibited -- http://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited -- http://www.icann.org/epp#clientUpdateProhibited
Domain Status: autoRenewPeriod -- http://www.icann.org/epp#autoRenewPeriod
Registrant ID:CR164143577
Registrant Name:nas coin
Registrant Organization:nascoin
Registrant Street: 1
Registrant City:Texuas
Registrant State/Province:Texas
Registrant Postal Code:10000
Registrant Country:US
Registrant Phone:+1.200200200000
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email:nascointeam@gmail.com if he had money loaded on his account or a CC on it, this works automatically. Also I think if he chose the 2 year option at the start, it would look like that. But, from expiration on March 24 to update on April 5 is almost 2 weeks, it is too much for an automatic renewal service, which should be done the same day of expiration or before (I think). But maybe you are right. i want to use some of my remaining server capacity to run another Nxt-based coin node. Are there any community rewards for running a NAS node?
We need forgers to make the network trusted. And forgers are people with a balance, whose big reward will be to get NAS on exchanges again. But, if I would want to pay you for a node, which would be the agreement?, what do you guarantee?, for how many time?, will you forge or just run a node?. |
|
|
|
Nas Coin creator, profile name Nas_Coin, is not dead. He renewed his domain, nascoin.org, 19 days ago, on April 5, after expiry date March 24. Surely he is following progress of Nas here. Domain Name:NASCOIN.ORG
Domain ID: D171574393-LROR
Creation Date: 2014-03-24T12:07:51Z
Updated Date: 2015-04-05T09:55:06Z
Registry Expiry Date: 2016-03-24T12:07:51Z
Sponsoring Registrar:GoDaddy.com, LLC (R91-LROR)
Sponsoring Registrar IANA ID: 146
WHOIS Server:
Referral URL:
Domain Status: clientDeleteProhibited -- http://www.icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited -- http://www.icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited -- http://www.icann.org/epp#clientUpdateProhibited
Domain Status: autoRenewPeriod -- http://www.icann.org/epp#autoRenewPeriod
Registrant ID:CR164143577
Registrant Name:nas coin
Registrant Organization:nascoin
Registrant Street: 1
Registrant City:Texuas
Registrant State/Province:Texas
Registrant Postal Code:10000
Registrant Country:US
Registrant Phone:+1.200200200000
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email:nascointeam@gmail.com |
|
|
|
Nas is Open Source now !!, we got the source code of NAS ClientI proudly announce that I was able to recreate the source code of the current Nas client. It is not exactly the same, it works slightly better because I deeply reviewed and tested all the changes from NXT version. And there is now also a core of 3 people with programming skills who will try to get Nas working and evolving: User1397367406, tiker and me, who worked together during the recent blockchain attack (a fork war), as well as we was the users who more contributed to revive the network, and we maintain independent trusted forger nodes. Everyone who join effort and skills will be welcomed. I pointed to the idea of recovering the sources long time ago. I repeated it after we got the blockchain synchronized, and several days later I wrote a brief plan, and I thought to do it myself: The plan could be: - 1. Compare sources of NAS 0.8.13(N1) with sources of NXT 0.8.13, to get which source files are different, and in which manner.
- 2. Implement the same changes to version 1.1.3 of NXT, compile, and test if it works the same as our current version of NAS. I'm afraid that here we will need to review malfunctioning things, like the test network, used ports, up-to-date peers, etc, the same way that I reviewed the config file.
- 3. If we get the source for 1.1.3 running properly, we can try the same changes for the last version of NXT.
Now the point 2 is done. I named the new version 1.1.3.N2, as our current working version is 1.1.3(N1). As corrected things, for example, you can notice that your current version doesn't show properly the incoming transactions information when you click on an account link, but it is properly displayed on this new version. Ports are also corrected to be different of NXT ones, using 7871, 7872 and 7873 for peer, UI and API servers. I started a public repository in order that everybody can get the sources, compile them, review them, and of course, modify them (either by pull requests here or by his own fork). So NAS is Open Source, at last! You can view and edit a Wiki for Nas, as well. Repository: https://bitbucket.org/patapato/nasIf you are not a developer, and you just want to update your client, you can get it ready from the Download menu, or by clicking this direct link: Download: Nas Client 1.1.3.N2You have to unzip it replacing your current instalation, it will keep your current database directory and file, nas/nxt_db/nxt.h2.db, as well as your custom config file, nas/conf/nas.properties). Or better you can do the opposite, to unzip it in a different location and then copy those 2 files into it. That way you keep your original installation if you want to get it back (take care not to overwrite the new default config file, nas-default.properties). If you don't have a custom config file, I recommend that you create it with the next lines, filling the first 2 if you want to announce your internet address, the third if you want to be a trusted forger, and the last one if you want to log debug information. I let the old UI enabled by default (I like it), but you can disable or enable it here too. File nas/conf/nas.properties: nas.myAddress=
nas.myPlatform=PC
nas.myHallmark=
nas.wellKnownPeers=cb2.flipflop.mooo.com; funkyvps3.funkymonkey.org; patapato.ddns.net
nas.knownBlacklistedPeers=
nas.enableUIServer=false
nas.debug=false
Lastly, if you are curious about the detailed changes from NXT to NAS in this version, read the contents of the changelog file here. I'm running and forging with the new client for more than one day. You can see it on the public server of tiker. This is a screen capture of it:  (EDIT) Donations are appreciated: NAS: NAS-H5AW-7J9F-7VCY-DJ8NB NXT: NXT-H5AW-7J9F-7VCY-DJ8NB BTC: 3Lgn75BAFS2yfmTzKmcD174ikXeYM5a2hC
|
|
|
|
NAS blockchain is riding again!!  Forging was stable and healthy for 2 days yet, one main fork with several forgers (at least 4). Some transactions were made without problems, with confirmations from other forgers. I like the old UI to see peers, the peer information is more complete and more clear in the old UI, so I put in my conf/nas.properties:
nas.enableUIServer=true
nas.uiServerPort=7872
and I connect to http://localhost:7872. Next image is what I see now, updating real time, very resdponsive UI. You can take the from here the peers that you want to put on nas.wellKnownPeers, in order that you get your client synchronized with the blockchain.  Compare it with the poorer information on the standard UI (few minutes before):  @tiker or @User1397367406, maybe you want to tell everybody something about how we got the blockchain to survive to the recent attack? |
|
|
|
How limit the java cache? My server does not support the war of forks.
Funny man you, lcharles123 . Go out from the dark side and join us, the "good guys", we are going to win to the "villain" soon , and the Nas network will work healthy again. Not bad at all to have this "stress test", as it is being useful to join forces, to understand weakness, failures and even bugs, to strengthen the Nas network, and to have now a core of new developers for the new life of Nas, with different views and criteria than the original ones. To everybody, wait few time, the network nodes are going to be synchronized again to the stronger and longer blockchain fork. Lesson learned, leasing balance for forging is not a good feature for PoS, we recommend to never lease again. Maybe we take out that feature from future versions of Nas. The trusting power of PoS is that an attacker needs to put his own stake on risk, but with leased stake, an attacker has nothing to risk, nothing to lose. Besides, the lease feature doesn't encourage more nodes on the network, on the contrary, it encourage the concentration of forging nodes, with the same potential problem as Bitcoin mining concentrated in few big pools. Beautiful words. You are welcome Then the rent balance may well set precedents for an attack, ...
It also set precedents for a defense. I will never rent again, and I will try to take renting out of the Nas software. The rental period ends in 80 blocks EDIT: the lease end, you can unblacklist my IP and redownload blocks. In fact, you are not blacklisted long ago, as it was unsuccessful. You earned a good fee for your work of testing the network in a war of forks. Keep it while Nas continue resurrecting, maybe you will buy a new server with it soon Would not divide the coins of the current fork equally among all the nodes to avoid war forks?
The bigger is the forger, the more trusted he is (because he risks more). But I will partially listen to you, I don't want to forge alone. |
|
|
|
How limit the java cache? My server does not support the war of forks.
Funny man you, lcharles123 . Go out from the dark side and join us, the "good guys", we are going to win to the "villain" soon , and the Nas network will work healthy again. Not bad at all to have this "stress test", as it is being useful to join forces, to understand weakness, failures and even bugs, to strengthen the Nas network, and to have now a core of new developers for the new life of Nas, with different views and criteria than the original ones. To everybody, wait few time, the network nodes are going to be synchronized again to the stronger and longer blockchain fork. Lesson learned, leasing balance for forging is not a good feature for PoS, we recommend to never lease again. Maybe we take out that feature from future versions of Nas. The trusting power of PoS is that an attacker needs to put his own stake on risk, but with leased stake, an attacker has nothing to risk, nothing to lose. Besides, the lease feature doesn't encourage more nodes on the network, on the contrary, it encourage the concentration of forging nodes, with the same potential problem as Bitcoin mining concentrated in few big pools. |
|
|
|
|
We keep trying to get the network in sync. Be patient. Now there are forks and we are very few forgers. But we was in worst situation before February, so keep waiting, Nas network is still weak but not dead, just ill ;-)
|
|
|
|
I tried to sync a client on my main computer, different from my forging node, and ended up with the above mentioned result. I wanted to see what would happen.
I re-started my forging node yesterday and stopped forging on it, it's still there doing nothing, at block 280284 4/7/2015 22:19:56, connected to 4 nodes: funkyvps3, patapato, 99.227.*.* and 106.187.*.*
The blockchain was not reset but i was forging all the block and so maybe i'm on my own fork.
Thank you User1397367406, I'm glad that you didn't reset your main forging node. I agree that better you stop forging until other forger reach you. I was on that situation before, forging alone ahead of the rest, and my node resynchronized by itself when others reached my block height: Hey!, I am synchronized again I didn't stop my node, just I stopped to forge and it synchronized after 5.5 hours, here is the block history of that time (GMT+1): ... 260632 18/03/2015 23:00:54 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 8708 % 260631 18/03/2015 22:59:17 0 0 0 NAS-5HZF-TPQ5-GSHF-7GV33 0 B 5386 % 260630 18/03/2015 16:29:59 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 2693 % 260629 18/03/2015 16:28:10 0 0 0 NAS-H5AW-7J9F-7VCY-DJ8NB 0 B 1482 % ... |
|
|
|
|
Edit: not correct post, sent very late with obfuscated mind, sorry.
|
|
|
|
Well, the problem, as I understand, is that lcharles123 has the power of forging with my balance for 1440 blocks, and his fork entered in a loop without end. Maybe it is not correct to ask others for blacklisting anybody. In that case, the solution by myself will be based on the same thing than the problem, that is, the fact that my forging power is > 80%. So, here is what I can do: - I setup another node, while keeping my original node intact
- I blacklist my original node patapato.ddns.net, and put nodes of lcharles123 and tiker as wellKnownPeers, in order to ensure that my new node sync with the other fork
- I wait to fully synchronize the forked blockchain
- I wait for the blockchain going back to the block 277935, the block in which lcharles123 forging power begins, as this fork is repeatedly going back to that block height
- In that client, in that moment, I transfer all my 22 M Nas stake to another account of myself, in order to take out all the forging power from lcharles123 in that fork
- I stop forging on my original client, in order to not conflict and let the block height grow in the forked chain
- I wait to the end of the leasing on that fork, at block height higher than 278461
- I restart forging on my original client (on this blockchain I didn't transfer my stake)
In that moment, the loop in that fork will be over, and I will not forge on it. So, it will be a fork with much less forging power and much lower block height. Anyway, the network should resync to one of both forks, and this time, if any forger try to go back with an old saved blockchain file he will not success. |
|
|
|
|
Your node disagrees with mine when your block height is over 277934. But it goes back to that height from time to time, and that block height is in agreement with my node. Your node disagrees just when there is a next 277935 block forged by lcharles123 node, or forged by you and confirmed by lcharles123 node.
My node is also stuck because there are no others confirming blocks higher than 279189, who was forged by User1397367406. So it will wait until some other forger reaches that height (that forger was User1397367406, but he reseted his blockchain confused by your case, sorry to say).
If User1397367406 also blacklist lcharles123 node, maybe your and his nodes agree on a different fork than me, but the network will synchronize by itself when you both reach my block height.
What is not healthy, and not logical (it is a weakness in NXT model of leasing) is that 2 nodes are forging at the same time with the same balance, as it is the present case. I mean, leasing period should be a time period, not a block height period, in order to avoid such a situation. Now we have to avoid that situation by ourselves, "by hand", and it should be by understanding all of you that, when somebody lease his balance for short time, it is for short TIME. If all of you agree with that, you should agree that the intended lease period should have already ended. The way to stop the unintended leasing period is to blacklist the unintended forger.
|
|
|
|
Blacklisting lcharles node might be a bit extreme. If it was done by lcharles setting his node then it probably wasn't intentional.
He recognizes explicitly that he restarts his node before the end-of-leasing block 278461, and he restarts it to a time after the beginning of leasing, with a copy made after he started to forge with leased balance. That is an intentional act, or better said, two intentional acts. The non intentional act is to let the node evolve by itself without reseting. Or at least, to reset his node to scratch, deleting his blockchain file in order to reconstruct a clean blockchain from the network. But reseting to a state between the 1440 blocks of his leased forging power is an intentional act. |
|
|
|
Our network is under attack (by lcharles123)(important Nxt and NEM community members, including main Nxt developer, don't like Nas) The attack consist of the following facts and steps: 1.- initially, there is a PoS network properly working, but forgers are few and distribution of forging power is:
· forger A: 22 M (me)
· forger B: 5 M (User1397367406)
· forger C: 5 k (tiker)
· others: < 1 k2.- the attacker asks for more forging power to forger A, by PM 3.- forger A leases his 22 M balance to the attacker for the minimum time, 1440 blocks, until block height EoL (End of Lease); attacker is now the forger with > 80% of forging power 4.- attacker makes a copy of blockchain file at the beginning of his leased time 5.- attacker forge blocks below EoL, then restart his node with the previously downloaded copy at the beginning of his lease, and waits for spontaneous fork, which is easy as he has most of the forging power 6.- lease ends on original blockchain, but lease never ends on his fork, as new blocks are rejected and reseted to the beginning of fork before reaching EoL on that fork 7.- main fork also doesn't advance, as his new blocks are also rejected and reseted to the last block with a transaction 8.- the network reaches a never ending situation, with 22 M stake forging on one fork and the same 22 M stake forging on another fork; Nas is fooled and attacker laughs loudly on us: My node crash.
It works well for a while, but it seems that gives peaks in memory.
The blockchain stuck height 278461, i'll have to download it again. :/
My node is no public:
nxt.servebeer.com
Notice that EoL block is precisely 278461 !, and he is downloading old copy of blockchain before that height in order to not losing his forging power: I leased my balance to account NAS-VBK9-5ZXA-CJQ8-GEWVU for 1440 blocks (he asked me for it by PM). The lease transaction was 9204069884770967256 at 02/04/2015 22:05:59 (GMT+1), and the lease started from block 277021 until block 278461. The blocks of problem for tiker are in the middle of this rank.
To worsen things, a trusted forger thought that he was on a bad fork, so he tried to reset his blockchain, stopping forging on his original blockchain and getting in sync with the attacker's fork: I tried syncing a client on my computer from mid march and so far it seems to sync until block 277934 and 277940 :
...
Solutions?:- I ask you, @User1397367406, to please recover your last original blockchain, as you forged in sync with me at least until height 279189 (06/04/2015 21:10:52, GMT+2), while you are currenly going back to 277934.
- I ask every forger to blacklist lcharles node: nxt.servebeer.com (46.105.44.4)
- I will distribute my account balance in smaller accounts, roughly the size of the next big forger, in order to have a more equilibrated distribution of forging power
Other suggestions, comments, ideas?
|
|
|
|
I think the bter.com node is stuck with my nodes.
But my node is in the longer chain. Several blocks under 279190 were forged by User1397367406 node (NAS-5HZF-TPQ5-GSHF-7GV33), and validated by mine. So, two big forgers with a hallmark agree until block height 279190, while yours is at 277941 now. I also notice that, when I stop forging, your blockchain goes on, gaining height (forged almost all by lcharles123 account), but when I restart forging, your blockchain goes back to near 277935. I notice another faulty thing, and I am beginning to understand (I'm afraid). lcharles123 has only 64 NAS, but he is forging with ~22 million NAS of effective balance. That is, lcharles123 is forging with my leased balance. But my leasing finished after 1440 blocks!! More properly, my leasing had to finish on block 278461, from block 277021. Here is the admin "Get Account" info of NAS-VBK9-5ZXA-CJQ8-GEWVU: {
"publicKey": "9b4c3453beb2707c7142e67a837dc8783607e209ce3992bcca1c37c7294ae111",
"lessors": [
"13029142609628990748"
],
"guaranteedBalanceNQT": "0",
"balanceNQT": "6400000000",
"accountRS": "NAS-VBK9-5ZXA-CJQ8-GEWVU",
"account": "17109047578379265575",
"effectiveBalanceNXT": 22109012,
"unconfirmedBalanceNQT": "6400000000",
"forgedBalanceNQT": "60100000000"
}Soooo... , I suggest you, @tiker, to blacklist the node of lcharles, as he is "ilegally" forging with my balance and confusing the network. And I ask you, @lcharles, to stop forging with my balance, as my leasing already finished on the longer fork of the blockchain. Otherwise I have to think that you asked me by PM a balance to forge with in order to just attacking the NAS network. |
|
|
|
|
