Hot answers tagged

18

Yes. You will have to create a separate asset for each item (kitty/land/area). The key part is that you currently can't change number of decimal places for assets on Stellar which are, by default, divisible to 7 decimal places. If you want your asset to be non-divisible, 0.0000001 of your asset will represent a single item. You will have to present it ...


11

Haven't tested it myself, but here is quote form Stellar documentation: Controlling asset holders As an anchor, you can mark the issuing account AUTHORIZATION REQUIRED. With this setting, the anchor must approve anyone who wants to hold its credit, allowing it to control who its customers are. Revoking access As an anchor, you can mark the ...


8

You can do this, but you'll have to create one additional account that supports the process (you can merge it with your account later so it shouldn't be a big problem). Let's say the accounts are as follows: D - your account (Derek) U - user's account S - support account Then the process looks like this: You send 800 exampleAsset to U. They can spend it ...


8

Yes. (See the Stellar website below.) And if you don't set an offer it will not be listed on sdex. I don't know what this means... You are the only one who can issue the asset so you are in full control of the "inflation". Issuing Assets | Stellar Developer Requiring or Revoking Authorization Accounts have several flags related to issuing assets. ...


8

I am one of the devs at Stellarport. The verified status means (like you are alluding to) that the domain has verified that it has indeed issued this asset. For example, any stellar account can issue a MOBI asset and add mobius.network as its home domain. How should you (the user) differentiate between the real MOBI and a fake MOBI? Enter verification - ...


7

This is fairly straightforward on Stellar, only taking a few steps. The theory we will take from Stellar's own guide to issuing assets The practice we can take from Mo's 'hacking-stellar' guide which uses his own 'lumen' CLI tool 1) Create an 'Issuing Account'. This is really nothing more than the account which will issue the asset. You DO NOT want this ...


7

Sure, it's possible. You'll need to setup your own server with database and pretty straight-forward logic. Setup listening to All Payments endpoint in streaming mode. In that way you can monitor all transactions on the network 24/7. Once the payment notification is received, just check the transferred asset. If it's not a "Bonus Token", just ignore the ...


7

Assets in Stellar network are represented as a pair that consists of: the code of the asset (ex. MOBI) the issuer account of the asset (ex. GA6HCMBLTZS5VYYBCATRBRZ3BZJMAFUDKYYF6AH6MVCMGWMRDNSWJPIH) Everyone can issue MOBI token from another account but the issuer part of the asset will be different. More info Assets Distributed exchange Issuing assets


6

Short answer: right now it's not possible as the way assets are represented is done using trust lines that by design don't distinguish between tokens. Convoluted answer: you could do it by issuing an asset per unique token (and you would issue only 1 of each). From a data set point of view it's workable (you would use the ASSET_TYPE_CREDIT_ALPHANUM12 asset ...


6

If you want to write a Stellar-powered solution, start with Stellar Development Guides. All tasks from your list are very basic and all of them are described in the documentation, so without any doubts you will be able to implement your case. Just copy-paste a few blocks of code from docs, change some constants here and there (like token name or issuing ...


5

Each account must have a trustline set before they will accept receiving the asset. When you hold an asset, you must trust the issuer to properly redeem its credit. Since users of Stellar will not want to trust just any issuer, accounts must explicitly trust an issuing account before they’re able to hold the issuer’s credit. This is due for a couple of ...


5

You can't freeze a specific amount of an asset on the account. However there is an approach that might help you with your case. I haven't it tried myself, but in theory it should work. Send 80% of total amount to user's account. Create one more account (let's name it "temporary"), establish trustline to your asset and then transfer the remaining 20% to ...


5

You can find all possible errors for operations in List of Operations doc. CHANGE_TRUST_INVALID_LIMIT -3 This operation would drop the limit of this trustline below the amount of the asset the account currently holds.


5

Disclaimer: Deleting assets can be dangerous since they may hold real value. Once they are deleted it may be impossible to get them back. Please be careful when deleting assets and only do so at your own risk. In order to delete the asset you will need to remove the asset from the system altogether, i.e. you will need to remove all tokens and trustlines. ...


5

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 ...


4

Correct. Each asset on the ledger is unique and identified by 3 parameters: Code Issuer address Type (alphanum4 or alphanum12) XLM itself is a special asset with type native.


4

Assets are related to each through offers on the DEX. If you make two standing offers to openly trade a pair of assets in both directions to set the trading value between them, then that relationship will stand so long as those offers exist. Others might make different offers at wildly varying relationships, which won't change the presence or value set on ...


4

Horizon /account/{account} endpoint returns current balances, including trust limit for each asset in the list. Each balance record looks like the following: { "balance": "126.8107491", "limit": "5000.0000000", "asset_type": "credit_alphanum4", "asset_code": "BAR", "asset_issuer": "GBAUUA74H4XOQYRSOW2RZUA4QL5PB37U3JS5NE3RTB2ELJVMIF5RLMAG" } In ...


4

I understand you are parsing /accounts/{id} endpoint. A single balance object is of the following form: { "balance": "0.0000000", "limit": "922337203685.4775807", "asset_type": "credit_alphanum4", "asset_code": "BTC", "asset_issuer": "GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH" } You are probably printing asset_type field only. You ...


4

Yes, this is correct. When we were designing Bifrost we had two options for Ethereum payments: Collect payments in a single Ethereum address. Generate a new address for each payment. We decided to implement the second option because the process is easier for users. In the first option users would have to add data to the transaction and this is an ...


4

If you want x and y to trust the same asset (not issued by either x or y) then you will need an account a to serve as the issuer account. If you want to continue to distribute tokens issued by the issuer account a after the issuer account has been locked then you will need a fourth account b to serve as the distributor account, which initially holds all ...


4

Here is a step-by-step process of the basic asset verification: Set home_domain field for your asset issuing account. Clients can look up a stellar.toml from this domain. This should be in the format of a fully qualified domain name such as example.com, anchor.example.com etc. DO NOT include scheme (i.e. http or https) and trailing relative path: https:/...


4

Transactions are containers which contain operations. Operations are what you're looking for. Try hitting https://horizon-testnet.stellar.org/accounts/GBMTGMQXBXZS5XJROQQOZB7TU4ACBIXTJJEG7WTXP4ZEARPGQGDWHWIS/operations?order=desc&limit=100 instead.


4

Pre-authorized transactions come with their own signing weights, so as long as they pass the medium threshold you're good to go. You do need to set them up before locking down the account though, so that limits you.


4

Asset stats are disabled by default, you can enable them with ENABLE_ASSET_STATS=true.


3

You'll need to run your own Stellar Core node, or query the third-party node using GraphQL interface. Information about all trustlines is located in the trustlines table of Core database.


3

No. New tokens on Stellar are created through adding a trustline with a Change Trust operation. You can set up as many trustlines as you want so long as you fulfil the minimum account balance (basically (2+x) * base reserve), and each trustline is affiliated with one issuer account ID; there is no one-to-one mapping between Stellar native currency and ...


3

Wanted to write a full, updated answer after doing a somewhat "deep dive" into this... not discounting @cesarm's answer at all! First of all, there was in fact an error in the docs. Note the PR recently merged here: https://github.com/stellar/docs/commit/8d06491910ceb8c6a9734a99ab2ea87bca635412 This change should show up on the website docs soon (if it is ...


3

Yes, it's possible. You can have multiple issuers issue assets with the same asset code. In order to achieve this, the "count collector account" would need to create trustlines for the same <asset_code> issued by each of issuer accounts. Then the issuer accounts can just send that <asset_code> (issued by themselves) to the count collector ...


3

The distribution account (b in your case) is optional. It is handy in most cases, because asset issuing logic can be fully separated from the distribution/trading/ICO logic. You can send your asset issued by a account directly to accounts x and y without any mediators. When you send custom asset from the issuing account to any other account, it issues an ...


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