Correct. Stellar is not a "global computer" like Ethereum, it's a ledger that has building blocks that let you provide guarantees about when a transaction will be valid in the future. "Executing" a smart contract involves submitting these transactions to the network when appropriate.
For instance, an "escrow contract" may involve pre-signed transactions ...
I understand from here and here that assets are defined by the unique combination of their asset_code and their asset_issuer.
If you understand this fully, you also understand Trustlines. An account holder has to decide that they trust a particular Steve before they can even hold SteveCoins.
To help identify the correct account to trust, Stellar ...
Tokens are created by simply sending them from the issuer account to anyone elses account. Your "Steve" account is unique and you are the only one in possession of the private key, nobody else can issue "Steve-SteveCoins". Anyone can issue "AlsoSteve-SteveCoins" but the tokens are not interoperable unless someone trusts both Steves and offers to exchange "...
what prevents non-Stevens from issuing dollars, bitcoins, coconuts, or SteveCoins they aren’t authorized to issue?
Who would authorize that? Stellar is decentralized, so there is no central authority blessing or condemning assets.
USD, CNY, BTC, ETH, LTC, XRP, and lots of other tokens/currencies have multiple issuers. There are some sketchy issuers and ...
Right now I believe SEP-7 is the best answer. It defines a link format that an app such as yours can use to create a transaction that you'd like a user's wallet to sign and submit. The flow is this:
User decides to buy something on your site
Your site generates a SEP-7 link with the appropriate payment transaction and shows it to the user
User clicks the ...
Your code is missing to set Keypair before send to friendbot.
var StellarSdk = require('stellar-sdk');
var pair = StellarSdk.Keypair.random();
console.log('secret => '+pair.secret());
console.log('public => '+new_addr);
I think there are two pieces of this question being conflated. There are assets in real life, and there are the representation of those assets over the network. The representation of assets on the network are transferred in an exchange. The new owner can keep it as an exchangeable representation over the network if they choose, or the new owner can redeem ...
There are currently no active plans with the Stellar Open Institute. Instead, we have other initiatives in the works.
To stay updated on what's coming, I recommend you sign up for the Stellar developer mailing list.
Check out the docs for Horizon, which is a RESTful API for gathering information about the network. It doesn't cost anything to make queries to it, but when building a real application, the best practice is to run your own Horizon instance to avoid centralization. Running Horizon implies running a core node, which has some nontrivial resource requirements, ...
Yes, you have to create this folder.
Stellar documentation explains it like this:
Here is a real world example that you can try out:
Ran into this issue today. I was able to check what the DATABASE_URL value that cmd horizon db migrate up expected by looking at horizon.env within the stellar/quickstart docker container. I then ran the command export DATABASE_URL=postgres://stellar:mypass@localhost/horizon && horizon db migrate up and migration was successful. Seems the env vars in ...
Unlike Ethereum, Stellar does not have automagic on chain contracts. You have to craft of chain transactions to achieve anything.
First read the official guides and especially get familiar with the stellar "transaction/contains operations" and assets concepts.
Then as a first start, go to stellar laboratory account creator where you can create as many ...
At the moment, there are no stellar-django packages.
Not sure what you mean here by "seed" but user data shouldn't be stored on any public facing endpoints/public facing endpoints. I think the answer you may be looking for is try implementing in browser signing instead.