Hot answers tagged

3

The function you linked to seems to be removing the transactions from a transaction set that have the lowest fees, until the set size equals 100. This corresponds with the documentation which states: Each Stellar node usually limits the number of transactions that it will propose to the network when a ledger closes. If too many transactions are submitted,...


3

It's just connection failures from/to some other nodes, you can safely ignore them if your node works fine otherwise. You can find out if your node is basically well connected to the network by looking at its connected peers via curl localhost:11626/peers. You should be connected to at least 8 (default config: TARGET_PEER_CONNECTIONS) other nodes.


2

11 is an internal error: An unknown error occured. You can find a list at: https://www.stellar.org/developers/guides/concepts/transactions.html#possible-errors


2

Altough I don't see a e.response property in your output and I'm not up to date with the latest js-sdk, I think it should still be e.response.data.extras try { await server.submitTransaction(...) } catch (e) { console.log(e.response.data.extras); }```


1

Unfortunately, if you set the weight of the account master key to 0, it is no longer able to authorize any operations. As you pointed out, the thresholds for operations are set to 1 on that account. So unfortunately, unless there are other signers on the account, you are no longer able to do anything with that account, including make a payment. For more ...


1

Nevermind, I've just realized my mistakes. They're right there: issuer identified twice, status use brackets, is_asset_anchor used brackets and fixed_number used brackets. Hope that helps future inquiries.


1

Without access to your private network it can be a little tricky to debug. This seems likely to be a problem with a corrupt bucket file, which can happen if there's an error or data loss during XDR IO. Bucket files are kept on the node's local disk as well as being published to archives. In versions before 11.4 we failed to call fsync() properly during ...


1

Sequence number for a new transaction must be the current sequence number +1. You can look up the current sequence number at: https://horizon.stellar.org/accounts/[ACCOUNT_ID] Given the fact you asked this question at 2020-04-28 06:42:22Z, the last (and for now only new) transaction on your account was at 2020-04-28T08:59:18Z and the current sequence number ...


1

The number of transactions per ledger is governed by a network wide setting that you need to change on a private network: look up the upgrades endpoint on the commands documentation.


1

The error object contains response field with HTTP response details from the server. You can refer to response.status to retrieve the status code. if (err.response && err.response.status === 404) { console.error('Account does not exist.') } else { console.error(err) }


1

When you don't set any path you still have a sendAsset and a destAsset, so the expected behavior is a conversion from one to another under the defined thresholds (destAmount and sendMax). You get this error because of course you there's not enough offer for the conversion to happen fully. In most cases you would want to omit the path attribute when one of ...


1

If you don't set path param then the path payment behavior is convert sendAsset to destAsset with default order book (between two assets). Unfortunately you have to "search" for path first and then "build the path" for path payment. Please notice that find payment paths still needs some work. I did multiple tests and finally I had to build a custom ...


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