Podcast #128: We chat with Kent C Dodds about why he loves React and discuss what life was like in the dark days before Git. Listen now.
8

Start the performance troubleshooting from pinpointing a bottleneck. During the test execution run top to get the list of the top resource consuming processes. There are 4 possible options: Your load testing app consumes 100% of CPU. Run the test loader app on a separate machine connected to the same local network to test Steall performance instead of test ...


6

I think I had run into the same issue, as Stellar Core by default uses a "fast-sync" mode (instead of "full-sync"). In terms of architecture, Horizon just takes the data stored at Core's DB, i.e. data that Core has processed. **It may be your Core did not process the record before ledger#400000, or at least your Core's DB does not possess the relevant ...


2

It says Can't have FAILURE_SAFETY=0 unless you also set UNSAFE_QUORUM=true. I guess you might have set somewhere FAILURE_SAFETY=0. In the example config, it says A value of 0 is only allowed if UNSAFE_QUORUM is set Therefore, your log showed Got an exception: SCP unsafe. To fix this, you have to declare UNSAFE_QUORUM=true. As you have 3 nodes, n=3 &...


2

You need to choose your private network first. StellarSdk.Network.use(new StellarSdk.Network('your_private_network_passphrase_here')) Then create an instance of StellarSdk.Server using the link to your local Horizon server. let stellarServer = new StellarSdk.Server('http://{horizon_instance_address}:{horizon_port}') And after that you can proceed with ...


1

It is mentioned in the documents that inflation money will be awarded twice in a week The inflation is distributed once per week, not twice. i don't know how its going to be work in private network. To run the inflation mechanism you need to submit a transaction containing an Inflation operation. Inflation process is not triggered automatically, so ...


1

1) Setup three stellar-core nodes and configure them in a way that you have your own network passphrase each node writes their own archive each node can read the other nodes archives they include each other in their quorum sets have each other in their known peers Kickstart your network by restarting one node with the force-scp option. 2) Get as many ...


1

Go straight with an example: suppose now, current ledger is #567 CATCHUP_COMPLETE=true -> The node gets data since the very beginning of your private chain, i.e. ledger #1, up to #567 CATCHUP_COMPLETE=false -> The node gets only recent data (e.g. & CATCHUP_RECENT=64 -> The node gets the data only from ledger #503 to #567) Now you are adding a 3rd ...


1

Using the JS-SDK you can do the following: Network.use(new Network(“Standalone Network; February 2017”)); Keypair.master().secret(); // your secret key


1

The secret seed for the master account is the sha256 hash of the network passphrase. e.g. "Standalone Network ; February 2017". KeyPair.fromSecretSeed(sha256(passphrase.getBytes(UTF_8)))


1

The NETWORK_PASSPHRASE should be made public, because it permutes how transactions are hashed. Since the passphrase determines the private key of the account containing the initial native tokens, however, you should obviously move those tokens to a different account before announcing your new network to other people. If you want the technical details, have ...


1

A copy of my reply from stackoverflow: After you have executed the steps in your question, stellar will be open to receiving transactions at localhost:8000/tx?blob=Base64 (See commands). You can confirm stellar is running with curl localhost:8000. The base64 blob is the the XDR encoded form of a transaction. In your case you will want that transaction to ...


1

I would recommend to start one-by-one with using port 11626 for one node first. If it works, then start the second one at another port. Stellar Core is the part to do network communication. Horizon & bridge server are like optional plugins building on top of the local Core, so you may omit them. Would you confirm that you are not behind a firewall? At ...


1

Had the same problem but it seems I figured it out. If you want the full history available on your horizon you need to do the following. Run your stellar-core with CATCHUP_COMPLETE=true. On your horizon side you need to manually tell it to ingest historical ledgers. Just starting horizon with --ingest=true is not enough as it will only ingest ledgers that ...


1

The issue was with the Core using an outdated version of the protocol. I had to upgrade the protocol to version 9 by using: stellar-core -c 'upgrades?mode=set&upgradetime=yyyy-mm-ddThh:mm:ss&protocolversion=9 So, just because you're running Core version 9 doesn't mean you're actually using version 9 protocol. The command above upgrades the network.


1

It looks like I hadn't set the passphrase in the code. The tx should look like the following: tx, herr := b.Transaction( b.SourceAccount{AddressOrSeed: from}, b.Network{"Network Passphrase""}, b.AutoSequence{SequenceProvider: client}, b.Payment( b.Destination{AddressOrSeed: to}, b.NativeAmount{Amount: "100"}, ), ) ...


1

I found solutions by myself. After create Stellar Private Network, We must execute command to upgrade protocolversion to 9. $ stellar-core -c 'upgrades?mode=set&upgradetime=2018-01-31T20:00:00Z&protocolversion=9'


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