Some wallets have the ability to input inflation destination (usually in the settings)
If your app does not offer you an option to set the Inflation
destination, you can do it manually by using the official Stellar
Laboratory. This will work for all wallets, including paper wallet.
Go to https://www.stellar.org/laboratory/#?network=public
A paper wallet is simply a public and private key that are written on paper, rather than stored digitally (in a text file or document).
You can create a paper wallet by any of the following methods:
Generating a new key pair using the official Account Viewer and then writing it down in a safe place.
Using the official Paper Wallet page to create a key pair ...
It's explained well in ledger support center here
Launch the Ledger Manager (click to see how to install and use it if you don't have it installed yet)
Connect your Nano S, enter your PIN, and stay on the dashboard
On the ledger manager, scroll down and click on the green bottom arrow icon near the Stellar logo
Confirm the installation if ...
You are right, the scheme you described is far from being secure. User should sign the transaction on the client-side.
I can see three options for your case:
Build and sign the transaction in the browser (that's what the most wallets doing). You can check the source code of existing web wallets for reference, most of them are open-source.
Prepare a ...
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 ...
Actually, you can setup simple flow by yourself. Check the "Streaming payment events" demo (https://www.stellar.org/developers/js-stellar-sdk/reference/examples.html#streaming-payment-events).
You just need to ask for the memo field, which allows you to track the inbound payments.
There is a Stellar checkout project registered for the next SBC already: ...
Something you could do is to host the site directly on github pages so users can inspect the code as well as clone the wallet and run it locally.
A project that has implemented this is Ark whose official web wallet is hosted on github.
Of course, someone could still hack into your github account and make a malicious commit that isn't caught fast enough by ...
I've been pushing the limits of data fields storing code and images, definitely a special viewer is required and in the case of code a virtual machine to run them.
Take a look here, this is code stored on a Stellar account in the data field:
The security considerations for choosing a Stellar Wallet is same as the ones you consider when storing other crypto assets.
Make sure you install an open source client/wallet whose code is audited and maintained by community members.
You can also install the wallets developed by their respective creators/foundations/companies.
The strongest wallets are ...
A private key is just a random 256-bit number.
A public key is just another 256-bit number, generated from a private key.
Quite simplified (and wrong in almost every way that matters), you generate a public key by
taking the hash of a private key
multiplying it with a point on an elliptic curve
keeping the y-coordinate
Both types of keys are encoded into ...
Most likely your CORS headers aren't setup, or setup incorrectly.
Websites are served on specific domains, and CORS header from an internet resource lets the browser know what domains are allowed to serve it.
Standalone apps don't care.
I think that currently the best way to store the keys to Stellar account in the form of a paper wallet is mnemonic code as described in SEP-0005. This Stellar Ecosystem Proposal describes how to derive the Stellar key pair from 12 - 24 words you can write down on a piece of paper or just memorize.
For example these 24 words:
reward result tennis clump ...
You have only two secure options and the first one is not as secure as the second one.
First, create a public/secret pair on the Stellar.org account viewer. This is the only web site that has our approval since it is the very own foundation's site. It may suffer from man-in-the-middle attacks, like malicious programs fishing for crypto accounts, shady ad ...
As a complementary to @Rubber Ducky's and @jehna1's excellent answers, I'll add some existing external tutorials which I think are more user friendly.
Set Up Your Lumen Inflation by Lumenaunts. it's essentially the same as @Rubber Ducky's answer however with some screenshots. This site also provides a couple of other nice tutorials for beginners.
You can also use the Stellar Horizon API to set your inflation destination yourself (without using a wallet app).
You need to create a new Operation and set options your operation to change the inflation destination that points to the wanted inflation destination.
async function voteFor(target, ...
The issuing account doesn't actually need anything other than the normal 1 XLM, but any wallet that is going to hold your token will have to add a trust line, and doing that will increase its minimum balance by the base reserve amount (currently 0.5 XLM). So a Lumen-only wallet has a minimum balance of 1 XLM, but a wallet with your token would need 1.5 XLM.
That's alright as long as your Master Secret Seed is truly random.
Remember that thousand of seeds is still a drop in the ocean of all possible keys.
Even though seeds will be sequential - you won't be able to tell that looking at public addresses, and there is no way to restore number of public addresses back into secrets/seeds even if you have full ...
This will take a little time, though, as there's a lot of requirement to get right like multi-signature and accurate description of every kind of operation.
Mooney is the first wallet to support uri schemes according to SEP-007.
However, it is only for payments, inflation, trustlines and offers, signing transactions will be available in version 2.0.
(This is one of my projects)
There is an operation called createAccount, and it's used to activate accounts with a starting balance. In fact all friendbot does is exactly what you are saying (it has a base account with a large balance and it does createAccount with 10000 lumens).
Here's some sample code:
It's up to the client whether to use particular federation lookup parameter or not. "I forgot to add the memo while sending funds to exchange, how can I get my lumens back?" – that's roughly 1/3 of all support requests from Stellar newcomers. Life would be much easier if all exchanges/anchors implement the federation protocol correctly.
To my mind, the ...
Any token can be sent with a payment operation. Creating a payment operation requires a destination address, an asset, and an amount. From the issuing account, submit a transaction with a payment to your wallet. The account you're sending to needs to have a trustline to the asset.
I am not clear what you want to do. As far I understand the questions is how users can hold my custom asset and XLM on the same account. In that case, here's one way how to do that
You already do auth_required and auth_revocable, let's keep that.
whenever a user signs up to you, create account and setup trusts for him as before.
on top of that, change their ...
I have the same.
Update: Found the answer on a redit page: https://www.reddit.com/r/Stellar/comments/f47o07/ledger_nano_and_account_viewer_doesnt_show_balance/
The latest ledger update is to blame, they are working on it. Check your balance on the Stellar blockchain explorer : https://stellar.expert/explorer/public/
using your public key in the search at ...
The person you are trying to send a token to has to set a trustline himself (with a change trust operation) to your issuing account. If his exchange wallet does not allow for it then he will have to use a different wallet that allows him to set trustlines.
To get a new address with the Ledger without doing custom work, you'll need to reset the ledger itself (which is probably not something you want to do).
When you reinstall apps, it will always generate that from some master private key that is used to regenerate same addresses for the different apps. Resetting the ledger will reset this master private key.
Send them to https://www.stellar.org/account-viewer and let them create their own accounts. Insist on saving their own public/secret key and not sharing it with any person or webpage.
Then ask them for the public key so you can send them one XLM in order to activate the account so they can check their balance and see everything is working fine.
Then they ...
If you want to make it secure, create a key pair directly in browser, and never send secret key over network (even if it's your own API).
With Stellar JS SDK:
//generate an account
var pair = StellarSdk.Keypair.random();