|
I'm confused totally. Are the new 0.9.2b version not working and we have to go back to 0.9.1b?
|
|
|
|
Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic. P.S. I'm not panicking at all, but IMO it was not right approach  Acknowledged, thank you for your continuous support and understanding! We'll do it properly next time! I know, its BETA, but Node's are real You probably missed the project Crypti, almost every day the network was not working. I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? We are not! And you are right, those NODES are real, and since the launch of the Beta version 0.1 till current 0.9b, NO collapses had occurred! Which i think deserves credit! I respect work of devs, no doubt about that. Just this time, when clients were "switched off the game" without announcement, was not good approach. That's only my opinion In any case, let's move forward |
|
|
|
I know, its BETA, but Node's are real You probably missed the project Crypti, almost every day the network was not working. I don't care about Crypti, I care about NODE. We aren't following bad examples, are we? |
|
|
|
In order to avoid problems in network synchronization, all clients must be the same version You cannot control what other people do. In NXT i still see clients of 0.x.x versions. Will NODE with different clients make their own network?  What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously. But it must be accepted by clients with the same version as mine?  Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Are we centralized? No, now the client works with 3-4 peers at the start to check the version, after which it connects to the following peers. Do you think if will not be the main peers and different versions of the clients the network to be divided into 2 or 3 parts Will the configuration file. You will be able to add their own nodes . as well as all linux clients will be the main peers when will the final version Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something? YES, You missed " BETA" status. These are precautionary measure in place until final release candidate. I know, its BETA, but Node's are real |
|
|
|
Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something?
We have not disconnected clients, the clients have verification on version while we're in beta, had also been in the early stages and the community knows. If the verification disable Your client to start and will work. But synchronization of the network will not work properly. Edit When will the final version and will not be network errors , we disable the verification and you will be able to work as usual. You must understand we launched POA now the whole network to be checked for stability. we need a version of early Yes, I understand, that NODE is in early state, but in future, things like it happened today should be informed before. People will start panic. P.S. I'm not panicking at all, but IMO it was not right approach |
|
|
|
In order to avoid problems in network synchronization, all clients must be the same version You cannot control what other people do. In NXT i still see clients of 0.x.x versions. Will NODE with different clients make their own network? What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously. But it must be accepted by clients with the same version as mine? Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Are we centralized? No, now the client works with 3-4 peers at the start to check the version, after which it connects to the following peers. Do you think if will not be the main peers and different versions of the clients the network to be divided into 2 or 3 parts Will the configuration file. You will be able to add their own nodes . as well as all linux clients will be the main peers when will the final version Sorry, didn't understand you well. Isn't it better to decide from which block fork will happen and old version clients will be on that fork or, from particular block, client will not work? Now it is thunder from the sky: no one client will work, wait for new client. This do not give trust for devs, devs can switch off all clients. I don't try to FUD, but this seems very bad for me. Maybe I missed something? |
|
|
|
In order to avoid problems in network synchronization, all clients must be the same version You cannot control what other people do. In NXT i still see clients of 0.x.x versions. Will NODE with different clients make their own network? What will happen if You are using an older version of the client, and I'm new. In our case, the transaction will not be accepted and will remain in your client, because the transaction is instant and the network must be synchronized continuously. But it must be accepted by clients with the same version as mine? Now there are several of them , but we plan to grow the network to increase to main 100-200.
Are they hardcoded in the client? Are we centralized? |
|
|
|
I noticed, that only two accounts forging last blocks. Can we state, that NODE PoA is easy gamed? |
|
|
|
|
Which block is the latest on main net with new version?
|
|
|
|
Launched + Synchronized the client for the first time. Can I play? DELETED
Sent some. Next time do not post address in thread |
|
|
|
So how can be stake registered right now? I havent registered yet but I have NEM adress.
Can I just put there my token and real NEM adress? Or is there some special process for late comers?
What is the deadline for the second stage of redemption? I'm really busy right now and don't want to miss out ...
No idea. It is not written anywhere. All I see here is a date of November 22, maybe the day after on November 23 is when coins are sent out to launch wallets? Info can be found both here: https://forum.nemcoin.com/index.php?topic=2631.msg8425#msg8425 and here: https://medium.com/@xtester/updated-phase-2-redemption-guide-401e63b43344And you're right, 22 November is the deadline. Thanks guys good to know I have a couple of weeks. I think it is a little rushed if even a crypto fanatic like me feels under pressure to claim the stakes and hopefully no one misses out  Should be extended in my opinion. afaik users who miss the deadline will be able to claim late but will be subject to a partial loss of coins. if users claim after 22nd of nov they will get 750k nem, after 23rd dec -> 500k, 23 jan -> 250k nem, 23rd feb - > 0 nem. It would be nice to know time and time zone, if the deadline date 22 of November. |
|
|
|
Step three:
I have a doubt: the address in green in the picture is different from the address in the left cornet of the client! which one is the real address? which one should i have to use?? Is there any way to make sure that the address in green that i've copied is correct? the address is the corner is testnet and the one you created is live net.. Livenet addresses start. With "N" where as test net start with "T". Once you have created and saved your data you can go to "verify account data" entrenched details and check that it is correct. You send off the address that gets created with the private and public key thx a lot! Now I have successfully registered my stake! But i really don't understand how i can send my NEMStake to NXT-97MX-EWKV-CGKX-DA5WH.... Do i have to use an nxt client?? pls, help me! Yes, you have to use NXT client. Latest version is here: https://nxtforum.org/nrs-releases/nrs-v1-3-2/ |
|
|
|
I have btt token registered and nxtEA stake transformed/sent, got real nem adress
starting with N and i have private key, now what? Should i do something tomorrow, if not, when?
Whaat?
you dont need to do anything with the asset exchange again if you have sent off your stake along with an address and saved the private key. for btt stake you will need to enter the token you used to register and an address into another portal and once you have done that you wont need to do anything else. i think the portal will be out tomorrow or the day after. Cool, sometimes is just bit difficult to find correct information from this huge sandbox ; ) I start from the beginning: DONE 1. registered phase 1 token from btt to bob.ninja.. 2. created real nem address in NEM client and send stake from NXT EA to this spesific account 3. saved keys and adresses NOT DONE YET Should i now go to: https://chain.nem.ninja/stakes/5. for btt stake creat real NEM address and ad it above page with my public key? 6. for NXT EA add alredy created NEM address and public key to above page 7. check that i am registered correctly from: https://chain.nem.ninja/stakes/registeredIs his correct or do i have wooden eye? did you send off the address you created in a message with your AE nemstake? you can use the same address for btt stake that you created for AE stake afaik. you dont send off public key. just address. go to https://chain.nem.ninja/stakes/ and enter your token and a live net nem address. Yes i send the created address, but i do find it in registered page..for this reason i thought that i made something wrong. if it is on the registered page then everything is ok. have you registered your btt stake using token and address? Maybe it is worth to display also amount of stake registered in the list? for example 1 stake, 1.5 stake an so on. It would be more clear for people, who register their BTT account and nemstake from AE. |
|
|
|
POA overall is still good, but there are a lot of problems, hope to solve as soon as possible
What is the problem ?. As a result, testing POA successful, we're going to move next week on a real network algorithm POA when deploying a real network algorithm POA ? What is time we can be used it ? I have tasked the team next week to release new clients for Linux and Windows in real networks, and client for exchange of currency that they could not participate in the Forge. I hope before the end of next week the real network will be transferred to the POA algorithm. Before the end of this week still available test network for testing What prevents exchanges to use normal client? |
|
|
|
And no 10% discount This ITO screwed totally  |
|
|
|
Administration office? http://127.0.0.1:7776/admin.htmlNHZ update and Blocknet announcement: The Blocknet: budget, development plans and accountability measures: http://downloads.xc-official.com/images/14-10-28%20The%20Blocknet-%20budget,%20development%20plan%20and%20accountability%20measures.pdfNHZ development is streaming ahead. We have been testing V 1.2.8 for over a week now, and everything is stable and we will be releasing for everyone on main net shortly. Things need to be properly tested to insure that everything is stable and working as intended. Major changes and design take time, so we appreciate your patience. The landing page is complete, and we are also just editing through the fine details. This page is intended to make the process of creating & accessing the NHZ wallet much easier for any new user, and supplying all the relevant information in one place. Beginning November 1'st, we will be starting our monthly 1,000,000 NHZ giveaway, so be sure to watch the social media channels, and NHZ forums for opportunities to collect some NHZ. So, no BLOCK shares on NHZ AE? |
|
|
|
|
Skillroad
Downloaded new POA testing version. Do I need to install it in C:\nxtl\ directory or it is not mandatory, it can be installed in other directory? I'm talking about Windows version.
Also, if nxtl directory is not mandatory, is it possible to run real and test nodes simultaneously?
|
|
|
|
The Financial Crimes Enforcement Network (FinCEN) today issued two administrative rulings regarding digital currency. And the government has apparently decided to go with the nuclear option. The first ruling published today relates to the application of FinCEN regulations to a virtual currency trading platform, while the second ruling discusses the application of FinCEN regulations to a virtual currency payment system. In ruling FIN-2014-R011, FinCEN states that any and all cryptocurrency exchanges must become licensed as a money transmitter including crypto-only exchanges:"As explained in the Guidance, a person is an exchanger and a money transmitter if the person accepts convertible virtual currency from one person and transmits it to another person as part of the acceptance and transfer of currency, funds, or other value that substitutes for currency." In ruling FIN-2014-R012, the agency confirms that any and all payment processors are obliged to register as money transmitters, significantly increasing the cost of entry in becoming a digital payments provider. "As described above, the Company is an exchanger under the Guidance because it engages as a business in accepting and converting the customer’s real currency into virtual currency for transmission to the merchant. The fact that the Company uses its cache of Bitcoin to pay the merchant is not relevant to whether it fits within the definition of money transmitter." Once labeled a money transmitter, a business wishing to continue operating must pay hundreds of thousands of dollars to become licensed in each of the 50 states. And that’s only the beginning of the regulatory costs and legal hoop jumping. In addition, companies are required to register with FinCEN, conduct a comprehensive risk assessment of its exposure to money laundering, implement an Anti-Money Laundering Program based on such risk assessment, and comply with various record keeping, reporting and transaction monitoring obligations, in addition to meeting several other requirements. It is interesting to note that the government classifies Bitcoin as a digital “property” for taxation purposes, but as a digital “money” for regulatory and licensing purposes. Full Story: http://altcoinpress.com/2014/10/fincen-ruling-us-government-ramps-up-war-on-cryptocurrency/Bolded red: there is already solution www.multigateway.orgStill Beta version. |
|
|
|
Hey everybody. I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM. Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]" This way we can keep the number of unclaimed NEMstakes to a minimum. I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week. Nevertheless it should be done, just so the people can't complain if they forget!! You cannot change the description once it is written in there. It is possible to send a message to every stakeholder. Maybe from the issuer but the issuer is UP and as you probably noticed he isn't here very often these days No need to be issuer to send messages to stakeholder NXT accounts. Everyone can send messages to everyone from personal NXT account. I thought there was a function for an issuer to automatically message all holders if his asset. You mean to manually send a message to all holder of NEMStake ? Yes manually. There is 482 stakeholders as for now. But I do not insist of doing it Maybe few days before deadline, it will be not so much Nemstake owners left. There is also possibility to send dividends automatically to shareholders. Possible to send 0.0000001 NXT as dividend with message in transaction. |
|
|
|
|
Show Posts
