appditto/natrium-wallet-server

Backend for the Natrium NANO Mobile Wallets

natrium-wallet-server's Issues

NANO-ARS price is not accurate

There are many USD prices in Argentina:

• Dólar Oficial: price defined arbitrarily by Argentine government
• Dólar Blue: price based on the street markets, aka "dólar informal"
• Dólar CCL: price based on financial bonds, aka "contado con liquidación"
• Dólar Bitcoin: price based on BTC-ARS and BTC-USD prices correlation

It seems Coingecko uses "Dólar Oficial" price, which is not accurate because only Argentine government is able to obtain USD at this price, nobody else can.

It would be more accurate to use "Dólar Blue" price, as it seems local exchanges and p2p are using that price as reference.

The website https://coinmonitor.info provides daily price information here

I have made branch which cointains a proof of concept, I will upload it soon

TypeError: expected str, bytes or os.PathLike object, not NoneType

Got this error

[1552494902] Starting NatriumCast Server...
Traceback (most recent call last):
  File "natriumcast.py", line 919, in <module>
    print(os.path.join(cert_dir, cert_crt_file), os.path.join(cert_dir, cert_key_file))
  File "/root/natrium-wallet-server/venv/lib/python3.6/posixpath.py", line 80, in join
    a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Suggested standard for transaction meta-data storage

With the Nano community we've developed a standardised json format for storing transaction meta-data. This information is not only useful to a user for understanding their own transaction history, but it would also form the basis for important functions like calculating capital gains tax or leaving paper trails, which are directly relevant to business adoption. If all Nano wallets would adopt this format it would smooth the third party application development.

Kindly take a look at this example:

{
  "version": "1.0",
  "accounts": [
    {
      "protocol":"Nano",
      "address": "nano_1ebq356ex7n5efth49o1p31r4fmuuoara5tmwduarg7b9jphyxsatr3ja6g8",
      "private_name":"Bob's gas n' grocery wallet",
      "public_name":"Bob Dobson",
      "modified": 1634718547,
      "accounting_unit": "USD",
      "protocol_spec":{
        "representative":"nano_1ebq356ex7n5efth49o1p31r4fmuuoara5tmwduarg7b9jphyxsatr3ja6g8"
       },
      "wallet_spec":{
         "wallet_name":"Natrium",
         "custom_fields":"Arbitrary data"
       },
      "transactions": [
        {
          "uid": "C1150C61D10C7E42F7F9494C205A924D0CEB55683F8BAA723C89DCC038E84C42",
          "identifier": "65146",
          "published": 1624430775,
          "confirmed": 1624430776,
          "sendrec":"send",
          "amount": 6782692307000000000000000000000,
          "value": 35.27,
          "memo": "10.003 gallons unleaded at pump #7",
          "transactee": "Circle K Gas Station, 2011 N Lincoln Ave, Urbana IL 61801",
          "protocol-spec":{
              "index":107,
              "transactee_address":"nano_1natrium1o3z5519ifou7xii8crpxpk8y65qmkih8e8bpsjri651oza8imdd"
           },
           "wallet_spec":{}
        }, ... ]
    }, ... ]
}

call back and nano-work-server is not working

my setup is:

Nano node on server 192.168.1.53 ports 7075 7076 7078
work server on 192.168.1.140:7076
Natrium server on 192.168.1.140:3000

Nano node working ok
work server working ok
Natrum server are not working callback & work server

on config-node.toml

[node.websocket]

# WebSocket server bind address
# type:string,ip
address = "::ffff:0.0.0.0"

# Enable or disable WebSocket server.
# type:bool
enable = true


[rpc]

# Enable or disable RPC
# type:bool
enable = true


[node]

# Enable or disable voting. Enabling this option requires additional system resources, namely increased CPU, bandwidth and disk usage.


enable_voting = true
work_threads = 0
work_peers = ["::ffff:192.168.1.140:7076"]

callback_address = "::ffff:192.168.1.140"
callback_port = "3000"
callback_target = "/callback"

if I use the callback on the git, the node doesn't start

"callback_address": "::ffff:192.168.1.140",
"callback_port": "3000",
"callback_target": "\/callback",

I also tried

[node.httpcallback]

# Callback address
# type:string,ip
address = "::ffff:192.168.1.140"

# Callback port number
# type:uint16
port = 3000

# Callback target path
# type:string,uri
target = "/callback"

envs from prinenv:

RPC_URL=http://192.168.1.153:7076
WORK_URL=http://localhost:7076 or 192.168.1.140:7076
NODE_WS_URL=ws://192.168.1.153:7078

appreciate all possible help thank you