Send an email to netstats@trustlines.foundation
Is there the option to use Geth?
Yes, this is possible via JSON RPC. The safest way to do that is to run your stuff in a docker container as well and add it to the same network as the node is (which would be tlbc_home-net).
The alternative is to expose/publish the JSON RPC port to the host machine. Then you wouldn't need to put your stuff in a docker machine. But in this case you should make sure the port is not accessible to the outside, otherwise you will almost certainly lose funds. The best way to do that is by using a firewall.
@block_producer_twitter --^
@block_producer_twitter Turns out there's an easier way: You can access the JSON RPC interface directly (e.g. with curl), but you need to find out the IP address that docker assigns to the container. You can do that with
docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' tlbc_home-node_1. Then use http://<ip address the command gave you>:8545 as endpoint for curl or whatever tool you're using
if you setup bare metal then it's AMD afaik
we are running the GRACEaid one on AWS
works a treat
let me see if I can find anything
alternatively look at running the DAppNode package
Ubuntu as an OS is fine. Additionally, we recommend at least 4GB of memory and 20GB of SSD storage as a minimum hardware setup to run the required services for a validator node (based on the experiences we have had on our long-running testnet). Please take into account that this excludes the Ethereum mainnet node. (see: https://medium.com/trustlines-foundation/t-x-launching-the-trustlines-blockchain-ffeb82b6989b). With regards to the bandwith I'll check with the devs and let you know once I know more!
Why we use Parity 2.3.6?
How to use bridge? I made tx in tlbc but who will create tx in eth mainnet submitTransaction like this one https://etherscan.io/tx/0x5135439d19e5baad1535ac6d055183758807c823b2d3a686b701e86f12413a50
can you verify 0x401 smart contract or at least ABI? https://explore.tlbc.trustlines.foundation/address/0x0000000000000000000000000000000000000401/contract_verifications/new
To use the bridge you need to send TLN (ERC20 token on the ethereum mainnet, https://etherscan.io/token/0x679131F591B4f369acB8cd8c51E68596806c3916) to the bridge (https://etherscan.io/address/0x18bdc736b23ff7294bed9fa988a1443357c7b0ed). The validators will then confirm this and release the tokens. This bridge works from ethereum mainnet -> Trustlines Blockchain.
We are working on verifying the 0x401 contract, but sadly it is currently not possible, either because of a misconfiguration or because of a bug in the blockscout software.
Meanwhile, if you need the abi, you can create it yourself from this contract. https://github.com/trustlines-protocol/blockchain/blob/master/contracts/contracts/bridge/HomeBridge.sol
Meanwhile, if you need the abi, you can create it yourself from this contract. https://github.com/trustlines-protocol/blockchain/blob/master/contracts/contracts/bridge/HomeBridge.sol
@k06a So I am not sure what you tried here https://explore.tlbc.trustlines.foundation/tx/0x9a8e71794b27a06e68a5c56459d9662908e049fe7e6a857793e661bc94698136/internal_transactions
Just tried to check how it works, ok. Will read smart contracts also.
