The friendbot takes care of funding accounts on the testnet. All you have to do is to send him your public key address.
You can do it manually via curl
or just look at one of the code examples in the official doc
Transactions can contain one or many operations being payments one of them, so your payment should be in the transaction history but you have to look for it whether in code following the links provided, with an explorer, or fetching the operation directly by its Id using the Stellar RPC url.
Even though you can generate keypairs(The seed and the public key) for an account...it will have 0 lumens to start with.
For funding purposes, you can use the friendbot. It will add 10000 Test lumens which can be used for testing purposes on the test network.
Stellar Friendbot Link
Addresses are the same no matter what network you are on.
Transaction hashes are different, however.
(The transaction hash pre-image is formed by taking the network ID, and appending the transaction envelope XDR to it.)
One way to monitor activity on the testnet is by keeping an eye on the Horizon fee stats endpoint (https://horizon-testnet.stellar.org/fee_stats) and adjust fees accordingly.
Earlier today the testnet was seeing a lot of activity causing surge pricing for fees to kick in (this was also affecting Friendbot at the time).
You can also visit the Stellar ...
You can say the transaction makes it into the ledger because the operations in the transaction are themselves balanced.
The main confusion is the example is transferring the amounts within itself.
If you start with 100 Apples in the account, then send 10,000,000 Apples (-10,000,000) to the account, and receive 10,000,000 Apples (+10,000,000) from the ...
The ledger is bit shifted (but I don't know the reason why). 697113 << 32 = 2994077536616448
This is from stellar-core source:
getStartingSequenceNumber(LedgerTxnHeader const& header)
return static_cast<uint64_t>(header.current().ledgerSeq) << 32;
Version 9.2 does not support version 10 of the protocol.
You can import a subset of the historical data (with command line catch-up), install the latest release candidate (10.0.0rc2 labeled "testing" in the quickstart image) or wait for a stable build (should be out in the next couple weeks).
It looks like you are looking for the /maintenance HTTP command. It cleans unnecessary Stellar Core history, including XDR buckets stored on disk and records in the database.
If you plan to use Horizon in conjunction with Core node, you will only have access to the recent Stellar history, as a complete history archive requires a fully-synced Horizon node (...
Hard to tell what went wrong:
You could check your account on Horizon directly: https://horizon-testnet.stellar.org/accounts/<your-address>
or use a different explorer https://testnet.steexp.com
In case you don't see a XLM balance on http://testnet.stellarchain.io/address/<your-address> your account does not exist (yet).
When you test, you ...
there are many ways to do it
here you can fund account directly with 10000 test xlm
copy and replace your public key and hit the url in browser 10000 xlm will be issued to your public key
do this programmitically pair.publickey is the public key ...
Yes you can find the Stellar's own account viewer for test and live in their site.
Here is the link for test:
TEST ACCOUNT VIEWER IN STELLAR
The same you can find for live if you switch at upper right corner to Public or you can access from the link:
LIVE ACCOUNT VIEWER IN STELLAR
a) I guess the easiest way should be to run your testnet node in a non persistent ephemeral mode and simply restart the container.
b) You could as well open a shell into your container and manually recreate everything similar to the package way.
# open container shell
docker exec -it [CONTAINER ID] /bin/bash
# stop core + horizon
Every transaction should have an XDR blob associated with it.
In order to troubleshoot your test transactions, you can breakdown the transaction you sent using the XDR Viewer on Stellar Laboratory
There's a lot to digest there but start with checking to make sure that the destination is correct, as well as the operation you performed is correct.
Your code is missing to set Keypair before send to friendbot.
var StellarSdk = require('stellar-sdk');
var pair = StellarSdk.Keypair.random();
console.log('secret => '+pair.secret());
console.log('public => '+new_addr);
Friendbot intermittently failing to fund account
The issue persists. Yesterday it worked, but today not.
Until they close this issue, I think it's safer for you to use "Create Account" operation with their given set to set up your account.
Step 1, Generate Keypair
Step 2, "Create Account" with the following pair (<= 1000 lumen acceptable?)
Creating and funding a test account using py-stellar-base:
from stellar_base.keypair import Keypair
kp = Keypair.random()
publickey = kp.address().decode()
r = requests.get('https://friendbot.stellar.org/?addr=' + publickey)
Resulted in this funded testnet account.
The recommended way to switch between networks is to not reuse directories and/or archives (unless you can guarantee that you can delete all data). This particular error ... does not match previous NETWORK_PASSPHRASE ... will be cleared after running newdb as that command drops all tables in the database.
As for your later question, there is no vetting ...
First of all, you do not need your own validator node to setup a federation server. They are independent components within the Stellar ecosystem.
Second, please note that federation is a client-only protocol, which needs to be implemented in wallet / client applications. This means that when you enter for example joe*yourdomain.com as the destination ...
To make your case work:
First, use accountB to trust "ASTRO"(issued by accountA), and sign with accountB. This means that now accountA recognizes ASTRO.
Then, you may send this ASTRO(by accountA) freely to accountB.
On Stellar, there is an operation [Change Trust] that allows a user to "trust" an asset (or the other way, revoke the ...
It happens occasionally that the friendbot account is depleted. Mentioning it in one of the official channels (keybase is a good one) will usually get it refilled quick smart. It probably should be automatic on the test network.
FYI, this is the current friendbot account status. It has been refilled at this time of writing and can fund another ~99,300 ...
The costs are defined per network and are the same for any operation as described in the developer guides:
The fee for a transaction is the number of operations the transaction contains multiplied by the base fee, which is 100 stroops (0.00001 XLM).
The base reserve and base fee can change, but should not do so more than once every several ...