We’re rewarding the question askers & reputations are being recalculated! Read more.

Hot answers tagged

9

While I'm not sure why this happens, this is not a different hash, its just encoded in base64 >>> import base64 >>> base64.b64decode('jDOeFb2J5/jH1sdUuAFqICu6EqjNtKq+OcbJ4wUHqPM=').hex() '8c339e15bd89e7f8c7d6c754b8016a202bba12a8cdb4aabe39c6c9e30507a8f3'


7

Stellar allows you to store data on the blockchain in two ways: Attach data to an account: you can attach key/value pairs to an account. Each key/value pair you attach to an account raises the minimum account balance by 0.5 XLM. This is in place to disincentivize people from storing large amounts of data on the blockchain. Attach data to a transaction: you ...


7

Your question is similar to how the stellar documentation describes customer accounts, which has two recommended methods: Maintain a Stellar account for each customer. When a customer deposits money with your institution, you should pay an equivalent amount of your custom asset into the customer’s Stellar account from your base account. When a customer ...


4

The detail of a transaction's operations are encoded in the field envelope_xdr. You can decode this value to obtain the payments and other operations. For example, this transaction with memo "Fruitcakes for Iguanas" has an envelope_xdr that decodes to show the payment details. So if you can approach your problem by fetching transactions instead of payments ...


4

It definitely works, I did a PoC years ago doing just that. Search is going to be the complicated part, since Horizon doesn't really give you any easy way to filter out transactions based on their memo, unless you host a server yourself and talk directly to the database.


3

The memo is part of the transaction, it's never part of an operation. You can set a memo in any transaction no matter what kind of operations it contains, so a transaction with a memo and a manageOffer operation should work fine. You will find the reason for transaction failure in the horizon.submitTransaction calls response. It can be a bit tricky to ...


3

It looks like you are doing a symmetric encryption/decryption. For the particular case you described, a crypto hash may be a better choice. SHA256 returns exactly 32 bytes and features good collision-proof characteristics. So try to hash a username with SHA256 and store the result to memo. Of course, it can't be "decrypted", however, the hash can be ...


3

The memo is associated with the transaction, so you'll have to actually pull the transaction for each payment. Here is some code for how I've handled it in the past with the JS SDK: function watchForPayments(publicKey, { onPayment, cursor }) { const paymentsCallBuilder = server.payments().forAccount(publicKey); if (cursor) { paymentsCallBuilder....


2

I've made Payment Locator tool with public API that exactly matches your case. Some highlights: Lookup by transaction memo, amount, asset, source/destination account. Search by a single parameter or a complex criteria. All operations are supported: PAYMENT, PATH_PAYMENT, CREATE_ACCOUNT, MERGE_ACCOUNT. Find everything, no matter how long ago operations were ...


2

To start, much of the proposed above is based on trust rather than rules defined in an SSC. There are no measures preventing the consumer-to-consumer platform from just taking the money and leaving. I would recommend building a 3-Party SSC from some of the 2-Party SSC's available. In these examples, there are fail-safes in place that disincentive foul play. ...


2

We implemented federated accounts for our users as follows: All our users have one or more account codes that they can use together with our domain name to form a federated address of the form accountcode*inbot.io We have implemented a federation endpoint in our API that responds with the appropriate stellar address and memo in response to a query for a ...


2

The transaction has been immutably recorded on the Stellar ledger. Binance (and other similar destinations) use the memo to associate transactions with specific accounts on their platforms. You've sent them the funds, but they don't know who it's associated with. You'll have to contact their support to work through this issue.


2

There is nothing Stellar can do. The memo is used by Coinbase to associate the transaction to your account; you can't recall the transaction, and you can't update the memo after submission. You'll have to talk to Coinbase to get the funds to connect to the correct Coinbase account.


1

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


1

You will have to contact the exchange with these transaction details. They are the one's holding your funds and will be the only ones who can help you.


1

Memo is an abstract type that represents 5 different kinds of objects. The Java SDK does not define toString methods for these classes, so the printed output defaults to the toString method on Object. This is unhelpful, as you outlined. In order to print the memo text you first need to identify if the memo is of the right subtype, and then you need to cast ...


1

Just need to remember any changes to either the db or the cfg will require a restart of the federation server. I also turned off query caching in the db.


1

With your idea you are going to use transactions on the stellar network as a message system to pass the hash to the recipient(s). That should technically work fine as the field is there and it won't be modified. But on the other hand you pointed out already that it won't help the main purpose of storing and transferring assets for everybody when you address ...


1

If you want to use an account as database you could use manageData operations. If you want to identify transactions then the only option is the memo field or the attachments feature which is not stored on the blockchain.


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