Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    ecooo
    @huoni_sms_twitter
    The bridge needs a a connection to a(n) Ethereum mainnet node. Do you
    want to run a light node (1) (default) or do you already have a node
    running and want to connect via JSON rpc (2) ?
    what is best choose ´╝či only have 40GB SSD
    Bruno Škvorc
    @Swader
    Any idea when/if the trustlines app will be open sourced?
    Bruno Škvorc
    @Swader
    Answered in telegram, signing out of this now, ping me there if needed
    Bernd Bohmeier
    @berndbohmeier
    @huoni_sms_twitter the geth light client is light on resources and should only need 2-3 gb of storage
    this is the best option, if you not have already a running ethereum node, which is why it is the default.
    sun1534
    @sun1534
    I have TLC. Can I convert to TLN?
    cducrest
    @cducrest
    No, you would a bridge from the TLBC to Ethereum mainnet and it was not built. The reason it was not built is because the validator set changes on the TLBC are handled by logic not computable by a smart contract on the ethereum mainnet like hard forks. So it would be impossible in a trustless manner to replicate the validator set of TLBC on the Ethereum mainnet. This would be required for a bridge to work since validators need to acknowledge on ethereum mainnet that TLC were burned on TLBC to issue TLN on ethereum mainnet.
    intutkri2
    @intutkri2
    I have TLN How to convert them to TLC what is the price of TLC and where can I trade TLC ?
    Martin Effertz
    @meffertz_gitlab
    Hi guys, I'm trying trustlines, and I encountered an issue with docker-compose solution where it can't read 'keystore-password.txt' file, and throws IsADirectoryError (docker version is 19.03.1). Then I tried Relay server guide - install steps, and everything was working, but at the step ~/opt/py-eth-index/bin/ethindex importabi I get an ConnectionError for port 8545 even thou I'm running instance of trustlines/tlbc-node:release. Could you help me out ?
    Do you think it's an issue with docker version ?
    cducrest
    @cducrest

    Hi, thanks for trying stuff out!

    If the quickstart script, throws an error IsADirectoryError, it usually means the process was interrupted midway through at an unexpected place and was restarted. The script intends to create a file but doesn't have the right to do so / the file was created as a directory. I would try deleting the whole folder (called trustlines or tlbc usually) and restart the process if you do not mind. You can also try to delete only the file/directory it complains about and restart the script.

    As for the relay not being able to connect to the node, if you are running the node with docker, by default the ports 8545 and 8546 are not exposed (for security reasons). You would need to open the docker-compose file and add these lines under ports of home-node:

    services:
      home-node:
        ...
        ports:
          8545:8545
          8545:8545/udp
          8546:8546
          8546:8546/udp

    I am working on a way to make this process easier but am also busy with other things and this won't be ready soon enough :/

    Martin Effertz
    @meffertz_gitlab
    Thank you, that worked after a few tries, plus docker-compose update did a trick. How do you guys run ethindex runsync and ~/opt/relay/bin/tl-relay without docker, should I create in /etc/systemd/system/ services, or something similar?
    skyminert
    @skyminert
    Hi, not sure if this has already been asked. Is there a step-by-step guide for how to claim the TLN tokens if you are using a Gnosis Safe Smart Contract wallet (chrome extension/mobile version)?
    Can it be done with Etherscan?
    cducrest
    @cducrest
    Most of the time we run stuff with docker. But we have a development server that runs everything with systemd services.
    I am not aware of how Gnosis Safe wallets work, but afair you can do it with etherscan
    cducrest
    @cducrest
    You should first use the website: https://trustlines.foundation/merkle-drop.html
    Enter your address there and click on check eligibility, then click on claim tokens. It should connect to your web3 provider and you should be able to see the data required to claim the tokens.
    Then you can use whatever means to send a transaction from the address elligible to the merkle drop contract at address 0x0A6f0C541Be542c098B7Ee03C9C634f20BCf8422 with the correct data.