nano
Here are 291 public repositories matching this topic...
-
Updated
Sep 28, 2018 - JavaScript
-
Updated
May 28, 2020 - JavaScript
Hello!
I'd be great if there were ... the most recent information on that topic I've found is this one https://www.fltk.org/articles.php?L1352 from 2014, despite fltk being advertised prominently on the README.md of this repository .. are the instructions given there still valid?
Thanks for info and/or adding a few words on the topic!
Mathias
Add Prettier
You don't need to discuss code changes about formatting: indents, spaces or tabs, etc
The developer will add code changes with declared formatting which is available in Prettier config
Add Prettier with https://prettier.io/
It will autochange files and format them correctly for the project
The list still contains reps that are redundant or should not be advertised, e.g:
BitGrail, Nanex, Binance, Nanode.
The best solution would be if the app downloaded the recommended rep list from myNano.ninja.
It would also be good if the rep selection was a mandatory step in the account setup.
Thanks
-
Updated
Aug 26, 2019
-
Updated
Apr 2, 2019
-
Updated
Jun 30, 2020 - JavaScript
Hi - thanks for all of your work... I have several LGT8fs and love them..... except...
2 issues when using your package....
#1 - I cant load the bootloader...
Arduino: 1.8.10 (Linux), Board: "LGT8F328, 32 MHz internal, 328P-LQFP32 wemos-TTGO-XI"
/home/art/Downloads/arduino-1.8.10-linux64/arduino-1.8.10/hardware/tools/avr/bin/avrdude -C/home/art/Downloads/arduino-1.8.10-linux64/arduino-1.
-
Updated
Aug 21, 2018 - Go
-
Updated
Jul 4, 2020 - Python
-
Updated
Jun 1, 2020 - CoffeeScript
Sometimes when you copy and paste a Nano address, it will have extra spaces at the beginning or end of the string.
In these cases, nanocrawler's search button does nothing onclick, which is quite confusing for users.
This can easily be fixed by trimming all whitespaces from the beginning and end of the search string before checking if the entered string is a valid nano address.
The node prints this message when "::ffff:0.0.0.0" is set as address an control is enabled: WARNING: control-level RPCs are enabled on non-local address ::ffff:0.0.0.0, potentially allowing wallet access outside local computer
We should add more information on this in the documentation and include the link in the printed message.
If not using docker:
- A non-local address exposes the RP
-
Updated
Oct 1, 2019 - C
Documentation
-
Updated
Jul 8, 2020 - C
-
Updated
Jun 30, 2020 - Go
If instead of entering password to unlock wallet I click "Create New Wallet", there is no way to go back to entering password, I have to restart the app.
-
Updated
Jun 4, 2018 - Go
Improve this page
Add a description, image, and links to the nano topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the nano topic, visit your repo's landing page and select "manage topics."

In order to better propagate only live blocks to peers, we need to be able to classify blocks as either "new"/"active" or "existing" from the perspective of the network, but from our node.
One way we could accomplish this is to have representatives periodically emit a signed message that gives a fuzzy view into their complete ledger.
One way to construct this fuzzy view is to XOR the hash of