I don't think there is a classic money reward, but you will have other kind of reward/benefit.
I think you should run your own node if you created some service relying over stellar network.
This way you will connect to your horizon instead of using other service.
Furthermore you can configure your server to accept query only from your services.
Yes, Docker provides a simple way to incorporate stellar-core and horizon into your infrastructure so long as BUCKET_DIR_PATH, TMP_DIR_PATH, and the database are stored on persistent volumes.
First, decide whether you want your container to be part of the public, production Stellar network (referred to as the pubnet) or the test network (called testnet) ...
If you look at the stellar dashboard there's a list of validators. You will see names like FairX, IBM, Tempo, SatoshiPay, StellarPort etc. These are all businesses that are invested in the success of Stellar. Since it's very cheap to run a validator (it's comparable to running an email server) you don't need big incentives to become one. Just an interest in ...
As some have noted in other answers, there is no direct monetary incentive in maintaining a node. This isn't necessarily bad news: if you look at Bitcoin's proof-of-work - and especially at how it became centralised over time - then it makes some sense NOT to have a monetary incentive, and thus avoid the problems it can cause.
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 ...
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 ...
XDR is a binary encoding of structured data. It is represented as a base 64 encoded String in transaction responses.
You can decode base 64 encoded XDR using the laboratory.
If you can use the Scala SDK you can call SignedTransaction.decodeXDR(base64)(...
TL;DR: only expose port 11625 on stellar-core.
Stellar Core Port 11625
Port 11625 of stellar-core must be exposed outside your network to allow it to communicate with peers.
The stellar-core configuration file has a KNOWN_PEERS field which specifies the IPs and domains that your stellar-core node will try to connect to. This is how your node will register ...
For Linux-based systems logrotate is a standard option in such cases. Here you will find all details regarding installation and usage for your Linux distributive.
It allows to set up custom schedule for Stellar Core/Horizon log rotation. Example config:
It will recreate Stellar logs ...
Ripple and the Stellar Development Foundation are separate entities. They were both founded by Jed McCaleb. Ripple was founded as a private company in 2012. The SDF was formed some time after Jed left Ripple as a not-for-profit organisation. Whilst initially similar, the two payment protocols diverged significantly when Stellar was re-written. As far as I ...
The SQL database can be thought of as a simplified view of the ledger state stored in the bucket list. As such the only data that stellar core relies on is account based not transaction based.
Now there are a couple tables (txhistory and txfee) that contain transactions and their related metadata for the purpose of being exported to Horizon.
As you can ...
Last time I started the full sync on my server (dedicated i7, 64 RAM, SSD), it took around 2 days to complete. It was about a month ago, with Stellar Core v9.1.0 and Horizon v0.12.1.
With earlier versions before Stellar Core v9, the full sync process usually took more than 10 days to complete on my environment.
When CATCHUP_COMPLETE=true option set, ...
An archiver node is a special kind of node:
when it sees a quorum (based on other basic/full validators on the network), it publishes to an archive.
Publishing is done every 64 ledgers if it's in sync with the network. You can read more about this in the history documentation
The default configuration installed by stellar-core-postgres under /etc/stellar/stellar-core.cfg uses CATCHUP_RECENT=1024 so the initial synch should be completed in a few minutes, this is as long as your node is able to successfully connect to another Testnet node which has available open connection slots.
You should be able to track this and other errors ...
A shared db definitely makes a lot of sense for most production deployments, if you have access to RDS then it has some very convenient features, it takes care of backups, offers point in time recovery and if using HA you get a standby master too...
As well as using shared databases, you will want to run your Horizon and Core deployments on multiple servers ...
This is a bug.
Nothing changed on that front, 10.0.0 happens to perform a schema upgrade the same way we've done it before.
I opened https://github.com/stellar/stellar-core/issues/1791 with a workaround that should get you back in business.
If you could add some details to that issue with details that could help pinpoint the root cause, it would be great. ...
There are no specific requirements regarding issuing account locking. It's up to the issuing entity whether to lock account or not. Master key weight can be changed at any time, thus most anchors prefer to lock account only when everything was double-checked and the asset is ready for the tokensale.
Also consider changing account thresholds instead of ...
I believe that 6 hops constant is just a performance limitation as the complexity of path finding grows with each additional hop. Even 6 hops is an overkill in most situations because almost all path payment operations can be executed in 1 (direct path) or 2 (via XLM) hops.
Use of of the exchanges.
When it comes to actual withdrawal process it looks like this:
After registering an account in the exchange, go to Deposit section.
You will be presented a Stellar address and memo. Use your wallet to send a payment to that address and add memo to your transaction.
Always start by sending a small amount first (1-2 USD worth of ...
Each node has it's own unique NODE_SEED which is used for messages signing. It can be set in the config file. The seed used for generating the public key this node will be identified with in SCP (that's a node ID you mentioned).
If you don't specify the NODE_SEED parameter explicitly, it will be generated randomly on each startup.
To generate a new, ...
Start with 32 bytes
Add a byte of 0x30 as prefix 'G' (now you have 33 bytes)
Calculate the checksum (two bytes)
Add the checksum as suffix (now you have 35 bytes)
Convert them to base32
That's your public key
Apply the same but using 'S' (byte 0x90) as prefix for secret keys
Well, with your setup TPS rate depends on your private network configuration.
First of all, check maximum transactions per ledger parameter. If you have local Horizon node up and running, just navigate to https://horizon.stellar.org/ledgers/?order=desc&limit=1 (use your Horizon address instead of horizon.stellar.org). Locate the max_tx_set_size ...
As a practical matter, SCP's asymptotic security follows from the fact that it depends only on digital signatures (and hash functions) for security, and that these can be tuned to resist arbitrarily powerful attackers.
For example, you consider an attack in which every grain of sand on earth is a supercomputer attempting to break SCP a billion times per ...
That's a broad question. How can you guarantee that Google Mail is not hacked? Potentially, any service can be hacked, and not necessarily on the server side. For example, DNS hijacking allows hacker to redirect DNS queries to a malicious domain name server, by overriding a computer’s TCP/IP settings. This can be achieved through the use of malicious ...
To create accounts you create a transaction containing a createAccount operation.
Friendbot is only there to give you an initial sum of testnet XLMs. Nothing else.