by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Bruno Škvorc
    @Swader
    Ok, can't figure it out. Running a non-validator node, passed in localhost:30302 to the jsonRpc flag, it seems to be trying to send something, but then just fails with requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))
    Bernd Bohmeier
    @berndbohmeier
    The node where you want to deploy it, so TL node if you want to deploy on TL
    the rpc port is usually 8545. 30302 is the port for the peer2peer protocol
    Bruno Škvorc
    @Swader
    I want to add a new currency onto TL, so essentially add it into the app eventually, yes. Right now there is no other way to use a custom currency since the app isn't open source yet (right?) so I want to add my currency into the trustlines.app. I understand the first step to doing this is add currencynetwork via tl-deploy, that's what I'm trying to do. I am running a node now, but I never got friendly with docker so have no idea how to expose the ports from the quickstart script. Can you give me an RPC endpoint for TL of a live node for this deployment
    Bernd Bohmeier
    @berndbohmeier
    yes, you can connect to https://tlbc.rpc.anyblock.tools
    Bruno Škvorc
    @Swader
    That worked - error message now changed to insufficient funds. I assume I need TLN tokens instead of eth?
    Bernd Bohmeier
    @berndbohmeier
    yes, you need TLC on the Trustlines Blockchain
    Do you have some?
    Bruno Škvorc
    @Swader
    I have TLN on Eth. Can I convert to TLC? How much should I need for a currency deployment?
    How much should I burn approx?
    Bernd Bohmeier
    @berndbohmeier
    You can convert TLN to TLC by sending it to the bridge contract address https://etherscan.io/address/0x18bdc736b23ff7294bed9fa988a1443357c7b0ed
    Bruno Škvorc
    @Swader
    Just send or call burn?
    Bernd Bohmeier
    @berndbohmeier
    Send a normal ERC token transfer there
    0.01 TLN should be enough
    Make sure to send TLN, and not ETH :)
    it will then take approx ~10 blocks on ethereum and another 10 blocks on TLBC until your tokens arrive
    Bruno Škvorc
    @Swader
    Can the currencynetwork subcommand accept private key instead of keystore or only keystore?
    Bernd Bohmeier
    @berndbohmeier
    only keystore at the moment. You can either look for a tool to convert it, or if you are familiar with python use the function manually
    Bruno Škvorc
    @Swader
    Yep, I sent some TLC around so all good. But getting out of gas hits, even with 2.5m gas: https://explore.tlbc.trustlines.foundation/tx/0xe1ea36e9926cdbef5624021e61a24c6bfe3ccdae66fbea474a05bfb30f24dd78/internal_transactions
    Yay, I did it with 5.5m gas. Methinks you could do with some gas optimization 🙃 What's the next step to get it into the app?
    Tatu
    @Smokyish
    @Swader Please confirm/verify the code at https://explore.tlbc.trustlines.foundation and share the link/address so people can check ut abd let's talk, if it looks all good it shuyldn't be a problem to include the currency network on the kist that the Trustlines App currently uses 😊
    Bruno Škvorc
    @Swader
    Oh this, nope. I don't know where to find my source code.
    The tl-deploy tool didn't tell me it generated any source code, or where it would put it.
    Tatu
    @Smokyish
    I would think that you'd find it in the folder where you deployed it from?
    Bruno Škvorc
    @Swader
    Nope :/
    Bernd Bohmeier
    @berndbohmeier
    contract verification is not that straight forward sadly, as the code is spread across different files. We are working on something that should make that easier
    if you used default settings, these should be the right settings
    Bruno Škvorc
    @Swader
    "There was an error compiling your contract". Do I need to provide ABI encoded constructor args as well?
    Bernd Bohmeier
    @berndbohmeier
    Bruno Škvorc
    @Swader
    Yep, it passed when I dug out the defaults from the deploy tools source
    It needed an older EVM and solc
    @Smokyish what's next?
    Tatu
    @Smokyish
    @Swader So as we discussed in person already, we'll now check the currency network that you deployed and see if it could then be added to the list of currencies used in the Trustlines App :blush:
    Cypher Junk
    @cypherjunk_twitter
    Hi guys. I was working with Trustlines android app and I made some connections and transactions. I realized that no especial fee was charged or asked for making those transactions, which is something I didn't expect according to Trustlines presentations about TLC token and delegates. Why were my transactions fee-less?
    Tatu
    @Smokyish
    @cypherjunk_twitter If you're using TLBC and the default relay server in the app, the relay server delegate is currently subsidizing the fees. Meaning that the current relay server operator is paying the fees on your behalf, but nothing is stopping you from starting a relay server and acting as a delegate that collects fees :)
    Cypher Junk
    @cypherjunk_twitter
    @Smokyish You mean the default relay server is currently doing us a favor for nothing? Until when will it be as generous?
    Tatu
    @Smokyish
    @cypherjunk_twitter That is up to the relay server operator :)
    chromemonkeys
    @chromemonkeys

    hi guys setting up a relay server because i wanted to try out the REST API functions. I followed the instructions for the manual installation of the relay server and then also setup a node for the Laika testnet using the quickstart script.

    i run the tl-relay command and get the following error

      File "/home/ubuntu/environment/relay/venv/lib/python3.6/site-packages/psycopg2/__init__.py", line 126, in connect
        conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
    sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: No such file or directory
            Is the server running locally and accepting
            connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
    does this mean my node is not running correctly?
    im running Ubuntu on an EC2 server if thats useful.
    Bernd Bohmeier
    @berndbohmeier
    Hey, did you setup a postgres database? It looks like it is trying to connect to it, but can not. We use a postgres db to index the Blockchain events.
    We are currently changing/improving our documentation, so you might have stumbled across some missing docu. You can try this https://github.com/trustlines-protocol/relay/blob/master/docs/RelayServer.md. It should explain how to setup the missing db and the indexer program that fills the db.
    chromemonkeys
    @chromemonkeys
    hey thanks for the help. i followed the link and setup the postgre db, when i run ethindex runsync though i get a connection refused error
      File "/home/ubuntu/environment/relay/venv/lib/python3.6/site-packages/requests/adapters.py", line 516, in send
        raise ConnectionError(e, request=request)
    requests.exceptions.ConnectionError: HTTPConnectionPool(host='127.0.0.1', port=8545): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f149e21af28>: Failed to establish a new connection: [Errno 111] Connection refused',))
    running tl-relay throws the same error also
    Bernd Bohmeier
    @berndbohmeier
    this is because the quickstart script uses docker to setup all necessary components, and per default there is no port mapping to localhost:8545. You will need add that manually. Looks like this is not documented :/
    • Make sure that you have docker and docker-compose installed
    • Go to the folder that the quickstart script has created, this should be trustlines for laika, and open the file docker-compose.yaml
    • Add the line - 127.0.0.1:8545:8545 under ports in home-node, see https://docs.docker.com/compose/compose-file/#ports for more informations on this.
    • Recreate and restart the home-node: Run docker-compose up --build --force-recreate --no-deps -d home-node within folder trustlines
    After that, try to rerun the failed commands