Topic: [ANN][XRB]Cryptocurrency's killer app: RaiBlocks micropayments - page 85. (Read 775154 times)

Good afternoon. Need help with the NANO transaction. Sent NANO from Kucoin exchange to Binace they did not come. How can I be helped?

https://raiblocks.net/block/index.php?h=B05AD0867B24E428A8291F624D5D5D2C96C57B797D471521E31EDE05C680CA2D

Upcoming Transition to Universal Blocks
The release of Nano Node version 11 included support for Universal Blocks to be turned on via a “canary block”. In preparation for the canary block, the Core team asks all users operating default Nano nodes to upgrade to version 11. In certain cases where developers are using block_create, the block type will need to be changed from the existing four block types to state_block. If users have any questions please contact us in the #support channel on our official discord server.

Version 11.2 can be found here or can be run using our official Docker repo at nanocurrency/nano.

The current timeline for the canary block to be launched is on April 12th, 2018.

How the Nano Protocol is Upgraded
Nano, like any other cryptocurrency, is a protocol, an agreed upon standard that allows computers to communicate with each other and agree on data.

Bitcoin uses a blockchain as its public ledger database. By design, the blockchain is synchronous, where batches of transactions are appended to the Bitcoin blockchain in blocks that the entire network agrees on. Data (transactions) can only be added to the blockchain in discrete steps.

Nano uses a block-lattice, a directed acyclic graph (DAG), as it’s public ledger database. By design, the Nano block-lattice is asynchronous, where transactions can be added independent of other transactions occurring on the network.

All nodes on a cryptocurrency network upgrading their protocol at the same time is crucial to the consensus and consistency in the network. Blockchains accomplish this by programming into the node software an upgrade block-height. At the x’th block in the blockchain, all nodes utilizing the new software will switch over from the old protocol to the upgraded protocol.

Since Nano doesn’t have an exact blockheight that all nodes can agree upon, we need a different signaling method for all nodes to simultaneously upgrade their protocol.

The method we use is to send out a canary transaction. A canary transaction is no different than any other send/receive/change/open transaction; for the sake of this article, lets assume that the canary block is a 0 Nano send from a certain account chain in control by Nano Core to itself. This transaction is already formed and stored away, unbroadcasted, and waiting to be utilized. All nodes that are running the upgraded software will be listening for the hash, the digital fingerprint, of this block as the signal to switch on the upgraded protocol.

During the upcoming days the Core team will give more details on the upgrade and will be available to answer any questions on Reddit or Discord. Thank you for your continued support!

It has been few months since the rebranding took place but the title of the thread remained unchanged. Although OP isn't active on daily basis but periodically he appears on forum. I will suggest to edit the title and along with old a few words about Nano can be added for wider awareness for new people to have access to project without efforts.

That sucks. Last option would be to check your ip6tables for rules and to also tcpdump the packets to see where they're goin.

/sbin/iptables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --dport 7075 -j ACCEPT

/sbin/iptables -t filter -A OUTPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --sport 7075 -j ACCEPT

/sbin/ip6tables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A OUTPUT -p tcp --dport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A INPUT -p tcp --dport 7075 -j ACCEPT

/sbin/ip6tables -t filter -A OUTPUT -p udp --sport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A INPUT -p udp --sport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A OUTPUT -p tcp --sport 7075 -j ACCEPT
/sbin/ip6tables -t filter -A INPUT -p tcp --sport 7075 -j ACCEPT

Thank you for your answer.

I have done:

But it is the same

That's how it is. Most people are just here for the moons and lambos and not for the technology. They're better off chasing vaporwares and shilling them to unsuspecting community noobs than supporting projects who makes the difference. Nano is a top project bur everyone is after a 10x or 20x ico project with little to no development in place.

The output ports seems to be non-7075, maybe try using sport 7075 instead?

/sbin/iptables -t filter -A OUTPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --dport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p udp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A OUTPUT -p tcp --sport 7075 -j ACCEPT
/sbin/iptables -t filter -A INPUT -p tcp --sport 7075 -j ACCEPT

This is fact when price of any legit project are falling people don't touch it. We will see lot of people shouting moon and showing interest in buying when the price will start to increase again. If project is real and development is going on through thick and thick situations means buying time is at low. Nano works smoothly who has used it knows well.

Well the most clever ones will always get involved prior every hype. The projects works well and everyone will realize that

Yes, it is part of a larger firewall script where I close "everything" then re-open one by one each port I need (I have others software running on this server). Here is the beginning of the script:

Then I open the ports I need according to https://github.com/nanocurrency/raiblocks/wiki/Network-usage


The -t filter comes from the way the script starts and does works well will all other programs, I have been using this script for years. I suspect this is related to the UDP nature of the protocol but I have no idea.

Anyone out there has an iptable working script on Ubuntu ?

I also have in my logs:

This is fact when price of any legit project are falling people don't touch it. We will see lot of people shouting moon and showing interest in buying when the price will start to increase again. If project is real and development is going on through thick and thick situations means buying time is at low. Nano works smoothly who has used it knows well.

Honestly it's the firs time that I've encountered this guy, lol never really thought he'll be so butt hurt about what I said hahahaha I guess I hit a nerve well just like what the popular saying says the truth hurts lmao anyway thank you for teaching me about the ignore list mate, I've been on here for almost a year now but it's the first time that I used this feature. I also just check his post history and you're right he is indeed a joke, looking at his posts it really seems like he just created his account to talk bad about Nano well too bad for him, he can never put a great project down. I don't want to sound too full of myself but I was right he's just another newbie spreading FUD lol.

Been trying to use the NANO Wallet on Windows.

It's the worst Crypto wallet I ever used.

Chaotic.

I was interested into NANO but this clearly isn't good enough for adoption.

Plus, NANO rebranding was a mistake. "NANO" on Google gives millions of other results and XRB Raiblocks still gives way more intel than NANO.
Fail...

It has been a little bit over a week since version 11 of the Nano Node was released. Currently, around 45% of the network has been upgraded and is running the latest version.

We’ve been monitoring its rollout and working diligently with those reporting issues to diagnose, understand, test and patch bugs that were found. Our team would like to thank all users who have reported any issues they have faced to us, this engagement helps immensely to refine the Nano protocol.

Version 11 – patches and learnings

In version 11.2, found at https://github.com/nanocurrency/raiblocks/releases/tag/V11.2, we have fixed an issue where a cached value was being ignored and when recalculated would cause the node to crash.

Also, work generation was moved outside of database transactions, which could cause large database sizes if work generation was very slow or there were a lot of wallet operations.

Universal Blocks were not the cause of any of these nor was their future rollout via canary block affected.

Exchange questions

Exchanges running nodes are a unique situation due to the scale at which they operate. Our team is available 24/7 to answer any technical questions exchanges may have and to offer full support in resolving any issues they are facing. When a problem arises and it is brought to our attention, our team dedicates full resources to solve the issue as quickly as possible.

Two things to keep in mind:

1) Due to the nature of some questions or issues that arise that are internal to the exchanges’ business or sensitive in their nature, we do not feel it is appropriate to comment on the issues they are facing and we feel it is best to let exchanges to provide updates as they see fit.

2) Many coins that are forks of bitcoin or are ERC-20 tokens have a standard API and integration that exchanges are very familiar with. Because Nano is not a derivative project, our node and API are unique and may experience issues that other coins’ nodes do not.

As a final note, our team would like to extend our thanks to the Binance team for their professionalism, time and dedication in resolving the wallet issues we recently faced. Our team was able to diagnose their problem and get a fix in place, resulting in minimal downtime.