Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Bernd Bohmeier
    @berndbohmeier
    https://docs.docker.com/install/linux/linux-postinstall/
    then it should work
    for yarn that seems really weird, I dont know what you installed, how did you install that?. The version on ubuntu 10.04 should be 1.13.0
    can you try to remove it and reinstall it?
    Bernd Bohmeier
    @berndbohmeier
    Installing with sudo apt install yarn
    FYI we are discussing how we can improve our documentation, so that this will be easier in the future.
    Bernd Bohmeier
    @berndbohmeier
    * I meant ubuntu 19.04
    Henri Heinonen
    @HenriHeinonen

    for yarn problem, can you please run yarn info in the clientlib folder and post the output here?

    Now it works!
    henri@henri-VirtualBox:~/Asiakirjat/clientlib$ yarn info
    yarn info v1.15.2
    { name:
    'trustlines-clientlib',
    'dist-tags':
    { latest:
    '0.4.2',
    next:
    '0.1.2-next.20180816T100742Z.fdb2685.HEAD',
    dev:
    '0.4.3-0-dev.20190418T151117Z.e4ec0fe' },
    versions:
    [ '0.0.1',
    '0.1.0',
    '0.1.1',
    '0.1.2-dev.20180816T093610Z.7f62300.HEAD',
    '0.1.2-dev.20180816T103808Z.2e313bb.HEAD',
    '0.1.2-dev.20180817T100838Z.3438646.HEAD',
    '0.1.2-dev.20180817T101709Z.d1e6622.HEAD',
    '0.1.2-dev.20180820T070359Z.826cf38.HEAD',
    '0.1.2-next.20180816T100742Z.fdb2685.HEAD',
    '0.1.2',
    '0.1.3-dev.20180822T082547Z.24cba90.HEAD',
    '0.1.3-dev.20180822T102431Z.1969074.HEAD',
    '0.1.3-dev.20181009T153444Z.871eaa3.HEAD',
    '0.1.3-dev.20181011T124854Z.953e548.HEAD',
    '0.1.3-dev.20181113T171213Z.6d797ce.HEAD',
    '0.1.3-dev.20181114T123018Z.b2222c4.HEAD',
    '0.1.3-dev.20181114T140340Z.dfd8471.HEAD',
    '0.1.3',
    '0.1.4',
    '0.1.5-dev.20181114T152441Z.5f4d690.HEAD',
    '0.1.5-dev.20181114T155919Z.48fe055.HEAD',
    '0.1.5-dev.20181114T161947Z.c2ae077.HEAD',
    '0.2.0-dev.20181115T123614Z.959b6f9.HEAD',
    '0.2.0',
    '0.2.1-dev.20181115T132422Z.8798c79.HEAD',
    '0.2.1',
    '0.2.2-0-dev.20181115T132855Z.015d698.HEAD',
    '0.2.2-0-dev.20181130T153121Z.a71eef2.HEAD',
    '0.2.2-0-dev.20181130T164335Z.ce12130.HEAD',
    '0.2.2-0-dev.20181205T085901Z.87fb174.HEAD',
    '0.2.2-0-dev.20181205T161129Z.364804f.HEAD',
    '0.2.2-0-dev.20181211T074901Z.332295b.HEAD',
    '0.2.2-0-dev.20181211T100239Z.8df1728.HEAD',
    '0.2.2-0-dev.20181213T115912Z.b878235.HEAD',
    '0.2.2',
    '0.2.3-0',
    '0.2.3-0-dev.20181218T105243Z.da11882.HEAD',
    '0.2.3-0-dev.20181218T113352Z.83173ad.HEAD',
    '0.2.3-0-dev.20190103T094750Z.7a80dcc.HEAD',
    '0.2.3-0-dev.20190103T145740Z.f2cfdf3.HEAD',
    '0.2.3-0-dev.20190115T153223Z.2a980d2.develop',
    '0.2.3-0-dev.20190115T160817Z.ae4001d.develop',
    '0.2.3-0-dev.20190116T093637Z.f082941.develop',
    '0.2.3-0-dev.20190121T081412Z.e108eac.develop',
    '0.2.3-0-dev.20190124T110658Z.3c09440.develop',
    '0.2.3-0-dev.20190206T133014Z.0a2df72.develop',
    '0.2.3-0-dev.20190211T154519Z.9a4abc6.develop',
    '0.2.3-0-dev.20190212T164719Z.d830113.develop',
    '0.2.3-0-dev.20190214T121558Z.67cd815.develop',
    '0.3.0',
    '0.3.1-0-dev.20190215T094103Z.540df19.develop',
    '0.3.1-0-dev.20190215T095707Z.ebfe91d.develop',
    '0.3.1-0-dev.20190218T080704Z.fbbea39.develop',
    '0.3.1-0-dev.20190228T092245Z.38bbe25.develop',
    '0.3.1-0-dev.20190308T095219Z.ce986d5.develop',
    '0.3.1-0-dev.20190312T132411Z.585b7c9.develop',
    '0.3.1-0-dev.20190320T134048Z.c3753de.develop',
    '0.3.1-0-dev.20190322T140908Z.b45e062.develop',
    '0.3.1-0-dev.20190327T115420Z.e34adb5.develop',
    '0.3.1-0-dev.20190327T174347Z.98ce77e.develop',
    '0.3.1-0-dev.20190329T154941Z.f1b6bfa.develop',
    '0.3.1-0-dev.20190401T152935Z.be0e3de.develop',
    '0.3.1-0-dev.20190403T073929Z.4d933ad.develop',
    '0.4.0',
    '0.4.1-0-dev.20190417T143405Z.07adc8d',
    '0.4.1',
    '0.4.2-0-dev.20190417T150508Z.eb601b3',
    '0.4.2-0-dev.20190418T135212Z.62d9890',
    '0.4.2',
    '0.4.3-0-dev.20190418T151117Z.e4ec0fe' ],
    time:
    { created:
    '2018-08-01T09:18:19.472Z',
    '0.0.1':
    '2018-08-01T09:18:19.584Z',
    modified:
    '2019-04-18T15:22:02.476Z',
    '0.1.0':
    '2018-08-02T10:46:44.721Z',
    '0.1.1':
    '2018-08-02T16:54:51.813Z',
    '0.1.2':
    '2018-08-07T15:37:58.284Z',
    '0.1.2-dev.20180816T093610Z.7f62300.HEAD':
    '2018-08-16T09:40:47.935Z',
    '0.1.2-next.20180816T100742Z.fdb2685.HEAD':
    '2018-08-16T10:16:10.561Z',
    '0.1.2-dev.20180816T103808Z.2e313bb.HEAD':
    '2018-08-16T10:48:48.561Z',
    '0.1.2-dev.20180817T100838Z.3438646.HEAD':
    '2018-08-17T10:16:21.870Z',
    '0.1.2-dev.20180817T101709Z.d1e6622.HEAD':
    '2018

    I had to use this information to install yarn: https://vitux.com/how-to-install-yarn-npm-client-on-ubuntu-and-manage-dependencies-through-it/
    henri@henri-VirtualBox:~/Asiakirjat/clientlib$ yarn --version
    1.15.2
    I also fixed the Docker installation with your tips.
    Henri Heinonen
    @HenriHeinonen
    20190501-1950.jpg
    Any ideas why the network is not showing up? MetaMask is connected to Kovan network.
    I am trying to send trustline request of 100 to other party.
    "TypeError: network is undefined"
    Bernd Bohmeier
    @berndbohmeier
    To which relay server is your website connected to?
    Do you just use the metamask example as is and are connected to the local docker setup? Then you should also connect your metamask to your local setup (127.0.0.1:8545)
    Henri Heinonen
    @HenriHeinonen
    The website was connected to
    const tlNetwork1 = new trustlines.TLNetwork({
    port: 5000,
    path: 'api/v1',
    web3Provider: web3.currentProvider
    })
    This seems to work better:
    const tlNetwork1 = new trustlines.TLNetwork({
    protocol: 'https',
    host: 'relay0.testnet.trustlines.network',
    path: 'api/v1/',
    web3Provider: web3.currentProvider
    })
    Bernd Bohmeier
    @berndbohmeier
    Just make sure that the website is connected to a relay server that is connected to the same blockchain as your metamask. With those settings both is now connected to the setup on kovan run by us.
    You can also use the first settings, but then you need to make sure that your metamask is also connected to your localsetup (127.0.0.1:8545)
    Thanks for you patience, and let us know what you think!
    Jabulani Msimango
    @JabuMsimango_twitter
    Hi
    I got an email on Becoming a Laika Validator in which I had to set up and run a node... I have done all those steps and have received the address.
    My question now is: What do I do next?
    Bernd Bohmeier
    @berndbohmeier
    you should have also received a link to a survey (trustlines.limequery.com/...) where you need to enter your address. If you did that and received the confirmation email, you are all set. (keep you node running) After all new validator addresses are collected ( 30th of June 2019), a hard fork will be proposed to activate the new validators. With default settings your node will autoupdate and you will start validating.
    Jabulani Msimango
    @JabuMsimango_twitter
    Hi @berndbohmeier I got the confirmation email, and thank you for clarifying this.
    vuneo (A)
    @vuneo_twitter
    Hi!
    I'm not a developer, but a philosopher and a sociologist with many years of experience at activism on freedom and common democracy.
    Can you do with some help from me?
    I rode about the project, and it seems the right step forward to a P2P society.
    vuneo (A)
    @vuneo_twitter
    I see this chat it isnt much active.
    Please Contact me at https://twitter.com/vuneo if you feel like i can add something to the Project. Please dont mind i mostly tweet in spanish.
    Andreas Papazidis
    @MorganGR
    @_franzihei_twitter who is handling the credentials please?
    Franziska Heintel
    @_franzihei_twitter
    Hey Andreas! The Trustlines Foundation is handling the netstat credentials (if you mean those)?
    Somebody will shortly get back to you with login credentials, if they didn't already. :)
    Andreas Papazidis
    @MorganGR
    Thanks @_franzihei_twitter !
    Anton Bukov
    @k06a
    Hi, any chance to run validator node with different private key than participated in auction? Maybe make NFT for validators?
    jannikluhn
    @jannikluhn
    @k06a no, validators have to use the same private key for validating as they did in the auction. This is deliberate, the point is to make transferring a slot to a third party hard. Otherwise a single party could very easily buy up a majority of slots and take over the chain.
    Jacob Stenum Czepluch
    @czepluch
    How do I get netstats credentials that the new quickstart guide asks for?
    andfletcher
    @andfletcher
    The quickstart script shows you the Email address. It is netstats@trustlines.foundation . You need to request a login via that Email address.
    Andreas Papazidis
    @MorganGR
    I have emailed two weeks ago I think. Haven’t got a reply yet.
    andfletcher
    @andfletcher
    @MorganGR im sure you will get an answer once everything is ready
    Anton Bukov
    @k06a
    @jannikluhn it is not really comfortable to run beta software node with my regular wallet private key. May I ask for private key change manually?
    Andreas Papazidis
    @MorganGR
    Yes I’m sure @andfletcher !
    jannikluhn
    @jannikluhn
    @k06a I'm sorry, but this is not possible. The validator stake is locked in a trustless contract on Ethereum and we can't change the address there. That's why we suggested to create a dedicated address to participate in the auction.
    Blockproduction
    @Blockproduction
    sudo bash <(curl -L http://quickstart.tlbc.trustlines.foundation)
    % Total % Received % Xferd Average Speed Time Time Time Current
    Dload Upload Total Spent Left Speed
    0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0bash: /dev/fd/63: No such file or directory
    100 5 100 5 0 0 11 0 --:--:-- --:--:-- --:--:-- 11
    100 5 100 5 0 0 5 0 0:00:01 --:--:-- 0:00:01 5
    100 1826 100 1826 0 0 1779 0 0:00:01 0:00:01 --:--:-- 0
    (23) Failed writing body
    Bernd Bohmeier
    @berndbohmeier
    What happens if you run it without sudo? bash <(curl -L quickstart.tlbc.trustlines.foundation)
    This command does not work with sudo. It is meant to be run either by a normal user, this works, as long as you add you account to the docker group the script should explain that, or as root directly.
    If you want to run the script with sudo, download it first
    curl -L quickstart.tlbc.trustlines.foundation -o quickstart.sh. Then make it executable chmod +x quickstart.sh. Now you can execute it with sudo ./quickstart.sh
    Andreas Papazidis
    @MorganGR
    Do we need a password for the testnet? When can we have the password for mainnet? (Can we install without a password?)
    Bernd Bohmeier
    @berndbohmeier
    What password are you talking about, the one to encrypt your private key, or the one for the netstats service?
    Bernd Bohmeier
    @berndbohmeier
    You need a password to encrypt your private key into the keystore file for parity. However, this password can be freely choosen by you.
    You will only have to a ask for a login data for the netstats service if you want to report to it (mainnet or testnet). This is completely optional.