4

This working, untested Java code will print all transaction hashes from the preceding 24 hours: long ONE_DAY_IN_SECONDS = 60 * 60 * 24; DateTimeFormatter dateParser = DateTimeFormatter .ofPattern("yyyy-MM-dd'T'HH:mm:ss'Z'").withZone(ZoneId.of("UTC")); long now = ZonedDateTime.now().toEpochSecond(); Server server = new Server("https://horizon-testnet....


4

Not as part of the Stellar protocol -- time bounds just specify when the transaction is considered valid. It doesn't have anything to do with how you actually submit them. A timebounds with time of now + 2 hours as the minimum simply means "I will be invalid if you submit me before 2 hours, but valid if you submit me after 2 hours". It's up to you to submit ...


4

Inflation occurs when somebody (anybody) transacts the Inflation Operation and it has been at least 1 week since the last successful Inflation Operation. The calculations are performed at that time. The inflation pool is (number of lumens in existence)*(weekly inflation rate) + fee pool This amount is shared pro-rata amongst all accounts which meet the ...


4

Friendbot has some outages from time to time. Looks like it ran out of money this time. It usually does not take long for someone at SDF to fix it. You could follow keybase chat to stay up to date about this kind of issues. It is best practice to create only one account with friendbot (on testnet reset) and consecutive test accounts from that one on your ...


3

Transactions contain an arbitrary list of operations inside them. Typically there is just one operation, but it’s possible to have multiple (up to 100). This is the documentation I believe you're looking for: https://www.stellar.org/developers/guides/concepts/transactions.html#list-of-operations


3

When you use a Horizon server to submit a transaction, it preforms some basic checks of the transaction integrity before sending it over to Stellar core. For example, it checks if all mandatory fields (like "source account" or "account sequence") are set. On the contrary, Stellar core charges fees even for failed transactions. I assume, it's an intentional ...


3

If the start of the hash displayed by the ledger is the same of the one displayed on laboratory, then is just a visualization bug You can check here Just to be safe, after you sign a transaction, the signed xdr is shown on laboratory so you can review it before to post it on horizon This way, using the laboratory, even if you sign an “injected ...


3

Stellar Laboratory interacts with Horizon. It sends a request to /accounts/{account} endpoint to retrieve account details (sequence number in this case). Horizon exposes an API layer for interaction with data stored on the ledger. Moreover, Stellar lab (and all other web-based wallets) submit signed transactions to the Horizon server which then re-sends ...


2

It updates automatically after some time, no answers required :)


2

Maximum asset amount an account can hold is determined by the particular trustline settings and may be up to 922,337,203,685. Total asset supply is unlimited.


2

Figured out the solution, just write the password in the next line :) In /src/constants/network.js const NETWORK = { available: { test: { url: 'your url', networkObj: new Network('your passphrase'),


2

If you want just today's tx, just curl the Horizon "transaction" endpoint is ok. Example with testnet: https://horizon-testnet.stellar.org/transactions?order=desc Crawl the "next" page recursively to check if there are still tx created today. . By default, only 10 tx are listed in every page. You may increase it, for example, to 150: https://horizon-...


2

This isn't stellar lab. It is "account viewer" which ONLY works with XLM assets. you can use Stellar Laboratory to construct a payment or StellarX.


2

You can put multiple operations for different accounts (identified by the 'source' parameter in each operation) into the same transaction. If one operation fails then all operations will fail. Instead of sharing secrets, share the transaction and let everyone append their signature. XDR representation is the way to share a transaction. // tx object to xdr ...


2

I'm working on timed payments with Stellar. You can have a look at the testnet-version already: https://test.artspirit.com


1

It's possible, but you'll need one more Stellar account for this. Account QCHU (original account) will be unable to pay tx fees until you change the low threshold back to 0. Create one more Stellar account (let's call it "auxiliary" account) with minimum balance 1.1 XLM. Using Stellar Laboratory prepare a transaction Use auxiliary account public key as a ...


1

The memo value returned by Horizon is base64 encoded. You can decode the value with base64_decode.


1

You can put it wherever you want. In fact /tmp is the worst place to use since that is a temporary folder and everything in it may and will be wiped on every reboot on most systems. I'd put it to /etc/something or if you use the docker container it should probably better be in the persistent folder (afaik /opt/stellar/something).


1

The very first payment to an uninitialized account has to be performed with the createAccount operation.


1

You should debug the XDR serialisation stage. Something that should be a 64-bit integer is null. The one hint you get is that the field type is Hyper. This refers to 64-bit signed or unsigned integers in the XDR scheme. You can see the Hyper fields in the XDR serialisation code.


1

You are getting an error because of a bad sequence number. I know this because I decoded response.getResultXdr(). Here are some things you should know: When you call sourceAccount = server.accounts().account(source), sourceAccount will have the correct sequence number. When you call build(), the TransactionBuilder will increment the account's sequence ...


1

There's no built-in support for crowd funding targets. You'll have to build it yourself from the various building blocks available -- combinations of onchain transactions, and offchain logic that trigger sthem.


1

You're looking at the problem from the wrong end. The way Stellar solves this is by using cross-asset payments. You can send funds to someone as one asset, and pay it using another, automatically. You select which asset you want to receive, and the payer can select how they want to pay for it.


1

Interaction with Stellar (-based) blockchain should be done via Horizon. You need to deploy horizon server and set up it to your stellar-core node. Build it from repo https://github.com/stellar/horizon or use prebuilt binaries. Bind Horizon ports to External IP:port behind url with SSL certificate. In Stellar Laboratory you can add custom url: https://...


1

Stream is closed with 200 OK status after sending a specific number of events (as far as I remember: 10 events). Curl does not implement Server-Sent Events specification correctly. According to SSE spec client should reconnect to the stream if connection was closed. Another issue with your request is that you did not pass cursor parameter. In such case ...


1

First and foremost check out this. Good explanation of how assets are verified. Also, I have just setup my own coin to play around with this verification process. The steps I took: Add Stellar.TOML to my web domain Add domain to my issuing account Here is my asset on Stellarport: https://portal.stellarport.io/exchange/alphanum12/RobCoin/...


1

I'll admit, I am not the most familiar with the Python Stellar Base, however I have heard great things about it! Gave it a quick look and saw that it does have methods for parsing XDR. Take the Asset class for example. Here you can see we have a from_xdr_object method that takes in XDR and outputs an Asset. I believe this is the type of functionality you ...


1

The following code works with JS StellarSDK 0.8.0: this.server.trades().cursor('now').stream({ onmessage: function (message) { console.log(message) } }) It does not throw errors (as TradesCallBuilder is inherited from CallBuilder that features .stream() method), but it never receives any messages either. I assume that you are right, and ...


1

i think your best bet is to figure out how other networks are measuring their emissions and mimicking their model / implementation.


1

The purpose of setting the home domain on the account is to know where to fetch the stellar.toml. The /assets endpoint should be updated within a few minutes on a Horizon instance that is already fully caught up to the network.


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