Hot answers tagged

10

You can use the buyram action of system contract. The above transaction can be performed using cleos as shown below. cleos --url <jungle-testnet-url> system buyram <payer-account> <receiver-account> --kbytes 1000


8

In the current specification, each of the 21 Block Producers will produce 6 seconds worth of blocks (i.e. 12 blocks) before handing off to the next producer in the production order. Irreversibility is not determined by number of blocks, but by the number of producers who build on blocks. The protocol will tell you when a block becomes irreversible. Once ...


6

Found this in Telegram (credit goes to Greg Lee): Here's a list of community run testnets that I'm aware of: SuperHero TestNet: https://github.com/eosgreen/EOS.IO-Community-Testnet-Reactivation Jungle TestNet: https://github.com/CryptoLions/EOS-Jungle-Testnet Arrowhead TestNet: https://busy.org/@eluzgin/how-to-join-arrowhead-testnet-for-bp-candidates ...


5

UPDATED: Jungle is: http://dev.cryptolions.io/ Their github: https://github.com/CryptoLions/EOS-Jungle-Testnet


4

Thanks for making this post. I was planning to aggregate the information into bp-playbook to make deploying different testnets easy. Hack Til Dawn Hackathon Devnet genesis.json file { "initial_timestamp": "2018-03-01T12:00:00.000", "initial_key": "EOS8JRondNFTj2hyoNJ26vYDTqtjCUMHGpLBSHU6DFggswkSLR5q8", "initial_configuration": { "...


4

First of all 2.x is really old now. As of this writing you're better off with dawn 4.1. But you might have missed make install before trying to run your node. cd build sudo make install


3

Yes jungle testnet upgraded to 2.0 and before updating they have started account migration programme but it's ended now, and they have given manual migration form on this site https://jungletestnet.io/ to migrate your accounts.


3

This looks like a consequence of the incompatibility between EOSIO v.1.1.x and EOSFactory v1.1. EOSFactory v1.1 is compatible only with EOSIO v1.0.8 and v1.0.9, not higher (the assumptions made in the release notes turned out to be over-optimistic).


3

Each network has a genesis.json file. Start nodeos with that file and with --p2p-peer-address set to 1 or more nodes on that network.


3

In the current specification, each of the 21 Block Producers will produce 6 seconds worth of blocks (i.e. 12 blocks) before handing off to the next producer in the production order. (see bytemaster's answer below for more details)


3

It looks like the nodeos process is still running judging by this output: std::exception::what: bind: Address already in use (your current nodeos process is trying to use the same address/port that's being used by the previous process that never exited) Usually when this happens to me I find the process number with: ps aux | grep nodeos This will give ...


2

Testnets are currently run by the community, and steps to join them very by the testnet. A good place to start is the Community Testnet channel on Telegram: https://t.me/CommunityTestnet


2

If you want to launch a mode to work locally, you should try github.com/eoscanada/eos-bios .. it's a command line tool, you copy the config and boot with a single command: eos-bios boot --single You can use that tool to join the staged launches that are happening, which hopefully lead to the mainnet. They are being orchestrated in the Telegram channel ...


2

So you always have to stake something to have the account: First check that the creator account (e.g. accname1) has funds... ./cleos.sh get currency balance eosio.token accname1 ... and the output might be something like... 832.5970 EOS ...and then check what NET and CPU accname1 has remaining: ./cleos.sh get account accname1 e.g. privileged: false ...


2

Before you create the account in Scatter, you'll want to add your local testnet's chain ID and API endpoint (probably 127.0.0.1). From there, you can import your keys and create an account while setting the local testnet you just added as the chain of choice. Select New Network top right


2

First of all you should create a account on jungle testnet, you should also have a wallet already created in your system, in my case wallet path is: /home/nirdesh.choudhary/eosio-wallet after that you have to link you wallet to your account , if your keosd running port 8900 you can do like : make sure you store your keys in secure location private_key = "...


2

https://www.dfuse.io/en/blog/dfuse-supports-jungle-testnet-2.0 How dfuse is supporting Jungle 2.0 Testnet dfuse API provides a REST and WebSocket API, which you can connect to using dfuse. Read through the documentation to get started and apply for your free API key. EOS Canada also offers standard endpoints for nodeos: RPC API: https:/...


2

If you've already made an account, ensure you have imported it's private key with cleos wallet import *private key* That way we can sign transactions as we need, now we need a node API endpoint that's connected to the JungleTestnet, I've found 13.211.220.84:8888 Now we can simply deploy the contract with cleos like you do in the test net. cleos -u 13....


1

Assuming The cleos command is accessing the relevant wallet and blockchain service 'exchange' is an account created on your blockchain and your authorised to use such account like having it's keypair in your wallet service. Try throwing in the full path to your contract rather than the individual wast & abi file. E.g. If your working directory is /...


1

If you just want to run a dapp in sandbox environment you can run local EOS node (nodeos). It will contain only your data and will not sync all blocks from testchain. You can start by downloading binaries of EOSIO and EOSIO.CDT. and then simply starting local node through nodeos. By default local node will run on http://127.0.0.1:8888/


1

So, I found the solution. I have created text file containing all 3 actions: newaccount, buyrambytes and delegatebw. Provided all the data and called cleos push transaction filename.txt Here is my text file with the actual names replaced { "actions": [ { "account": "eosio", "name": "newaccount", "authorization": [ { ...


1

Yes, it is possible. You can view the related EOS-JS documentation at the following link: https://github.com/EOSIO/eosjs/blob/e53c0e0bf791c22818ee3c9ea3592bcf1c0877ec/docs/2.-Transaction-Examples.md#create-new-account-multiple-actions Create New Account (multiple actions) const result = await api.transact({ actions: [{ account: 'eosio', name: '...


1

You can connect your eosjs or cleos with public api nodes and there is not any api key needed it's also not rate limited. For test public api nodes you can directly ping here and you will get list of api nodes. For mainnet please refer this official documentation by eosio.


1

I think you are not very familiar with eosio i suggest to read https://developers.eos.io/eosio-home/docs this documentation.


1

Most of the testnet just uses the same fee and ram policy as the mainnet. On testnet, you can just easily ask for faucet tokens for your test. The Junlge Testnet is the most popular one. However, if you really need a network environment with cheaper fees and ram fees for any reason, you might want to consider implementing your own network with modified ...


1

The above answer is perfect. Anyway, to buy RAM for myself, in my local node on the Jungle Testnet, I use the following code: ./cleos.sh system buyram <myaccountname> <myaccountname> --kbytes 200


1

I think you could copy out the data in ~/.local/share/eosio/nodeos/data/ which are two directories blocks and state. Restoring these two directories to a previous state should make it work again. Be sure to have stopped nodeos before copying the stuff out. If you stop nodeos like normal I don't see why it wouldn't restart like normal if you restore these ...


1

The built-in keypair of eosio is set as follows. You can also solve this problem by importing this key. 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3 EOS6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV This keypair is created automatically when you create a wallet. I do not use v1.0.5, so I do not know if this is the case.


1

I found this line in the code: https://github.com/EOSIO/eos/blob/master/contracts/eosio.system/eosio.system.cpp#L126 2. new accounts must stake a minimal number of tokens (as set in system parameters) therefore, this method will execute an inline buyram from receiver for newacnt in an amount equal to the current new account creation fee.


1

I like to analyze the full Jungle TestNet script. It really allows you to understand how to create a block producer node and how to connect to existent ones. Check http://dev.cryptolions.io/#home -- after you register as a BP you will receive a nice script. Or just check my outdated one: https://gist.github.com/leordev/1e12b229c28735e9defbd6249e4108c5 ...


Only top voted, non community-wiki answers of a minimum length are eligible