16
General Discussion / Re: Ideas for a redesig of the fee architecture
« on: April 05, 2016, 08:11:30 pm »
My preference would be to eliminate all fees and SIMPLIFY the role of committee members not make it more complicated.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Who are these investors let in on the ground floor? Were they Brownie holders? I'm a brownie holder and didn't here anything about this opportunity.
I don't like private profits being made from something that should be a core feature of bitshares.
I understand and appreciate that @onceuponatime has taken on risk and reduced sell pressure on BTS get Stealth asset implemented but I think this feature would be better as just a standard feature .
I'd like to see @onceuponatime to sell this feature to bitshares and delete the Stealth asset.
He could sell it for whatever he paid +25% to cover costs and make a profit. This could be done as a worker proposal.
I've never thought Fee Backed Assets for core bitshares functions made any sense whatsoever.
I assume Steem will largly be based on graphene...
Has a sharedrop (on bts) been discussed before?
as for how to actually use this -- if anyone on the network does one of the stealth ops, the fees will be accumulated in an object and then sent to stealth-buyback account at the next maintenance interval. a v-op will be produced at that time (so you only get one v-op per maint interval instead of spamming the stealth-buyback history every time someone does a stealth tx). during each maintenance interval stealth-buyback account automatically attempts to use its BTS balance to buy as much STEALTH as possible on the market, generating a market order v-op (immediately followed by a cancel v-op if it can't be fully matched). you can basically monitor the stealth-buyback account history if you're interested in the finance. (ok, i guess technically that's up to three v-ops per maint interval total)
So, the important question is:
Can I use stealth transactions or not?.. I dont see any options at the GUI and all the Tokens still belong to BM..
Code: [Select]# First Steps for End-Users
https://gist.github.com/099201101b397be076d4f9d0bf5e7e33
This guide gives a quick introduction on how to trade STEEM:BTC in BitShares.
## Choose your wallet
To interact with the BitShares ecosystem, you can either
* [download the official Light Wallet](https://bitshares.org/download)
* or access the network in the browsers via one of our partners:
* https://openledger.info
* https://secure.freedomledger.com
* https://bitshares.org/wallet
## Create an account
In order to use BitShares, you will need to register an account. All you need
to provide is
* an account name
* a password
The identicon at the top cn be used to verify your account name to third
parties. It is derived from your acocunt name and gives a second verification
factor. And this is how you register your account:
![Create a new account](http://docs.bitshares.org/_images/create-account.png)
Note that, in contrast to any other platform you have ever used:
Creating an account at one of our partners will make your account
available at all the other partners as well.**
Hence, your account name can be seen similar to a mail address in such that it
is **unique** and every participant in the BitShares network can interact with
you independent of the actual partner providing the wallet.
## Backup your account
Since you are the only individual that has access to your account and funds, it
is **your responsibility** to make a secure backup of your registered account.
After creating your account, follow these steps:
1. Click the *Backup required* link in the footer
![Backup required footer](http://i.imgur.com/WMI04fc.png)
2. Click "Create Backup"
3. Click "Download" and store the file safely. Make sure to **remember the passphrase** you provided when you created your wallet (above) as the downloaded file is encrypted with it.
4. (optionally but recommended) Note the `xxxxxx * SHA1` checksum to verify the backup
## Depositing Bitcoin
1. Click on **Account** in the top navigation bar to open up your account overview
2. Make sure it states `(Your Account)` below your account name
3. Click **Deposit/Withdraw** to open the corresponding page
4. Enable the *gateway* **CCEDK** which provide the most liquid `OPEN.BTC` IOU
Note: OPEN.BTC is an *I owe you* (IOU) provided by CCEDK. This means that they back every `OPEN.BTC` token with 100% reserves!
5. Identify the `OPEN.BTC` row and use the provided Bitcoin address to fund your account with BTC
6. After reception and confirmation of your transfer, you will be automatically credited with `OPEN.BTC`
![Depositing BTC](http://i.imgur.com/tuO0LFg.png)
## Trading OPEN.BTC for STEEM
1. Clicking the **Trade** link in the top navigation bar will open the decentralized exchange of BitShares
2. Since any two assets can be traded, we first need to search for our `STEEM:OPEN.BTC` pair by clicking **Find Markets**
3. Search for `STEEM:OPEN.BTC` to trade `STEEM` for `OPEN.BTC` (the tokens you have received for depositing `BTC`)
4. Click on the search result below to open the market page
![Identify the STEEM:OPEN.BTC market](http://i.imgur.com/DE4USPk.png)
5. Similar to other exchanges, you can now place buy and sell orders at your price.
**Note:** In BitShares, placing an order costs a very small fee (sub-$cent) which get a 90% refund on cancellation. This fee can be payed in almost any asset including `OPEN.BTC`, `BTS` or `STEEM` and it is up to you to decide which asset to use to pay for the fee. Further percentage fees on filled orders may apply.
![Playing Buy and Sell Orders](http://i.imgur.com/lycrX2e.png)
6. Once your order is matched, the corresponding asset will automatically be credited in your account.
If I make this tutorial video, do I assume that the user already has a BitShares accounts?For me it would make sense separating the two, maybe titled
Or does it need to include instructions on how to set that up first?
1) Wallet install and set up
2) Funding your BTS Wallet
It could be that the transaction was broadcast too late to be included by the producer. There is a race condition where if you broadcast it, but the producer doesn't receive it in time and so it is "stale" and not included in the blockchain.
Thanks for the explanation. Does "in time" mean that a POW based on the hash of block n is only accepted if it is included in block n+1?
That would severely (and unnecessarily IMO) punish miners on a "high"-latency connection. For example, with a (perfectly normal) latency of 300ms a miner can effectively only mine from t+0.3s until t+2.7s, which is a 20% reduction of efficiency!
Moreover, this means that the currently active witnesses automatically have a higher than average chance to have their own POWs included in the chain in time.
Even worse, it means that the currently active witnesses can deliberately drop POWs from other miners, thereby increasing their own effective hashrate!
IMO there's no reason to not accept POWs that are based on the hash of one of the latest 21 blocks (for example).
There is something not working here.With pow you only mine a 'ticket' in the block production queue .. once you got a ticket mined you need to wait for your round to actually produce a few blocks .. (maybe 20 or so)
I've been mining since yesterday with my quad-core at ~22khps. The client tells me it'll take 50-150 minutes to solve a POW. Indeed I sometimes see a message like "Broadcasting Proof of Work for cyrano", but that's it. No accumulating STEEM, not even POW transactions in my account history (except for one yesterday, almost immediately after I started).
Any ideas?
I know that. I should be mining a ticket every 2 hours or so, but I'm not.
What I'm seeing is messages like this:Code: [Select]hash rate: 21507 hps target: 27 queue: 95 estimated time to produce: 104.01088637807846737 minutes
and in the 30 hours I've been mining a grand total of 5 messages likeCode: [Select]Broadcasting Proof of Work for cyrano
If I understand this correctly each "Broadcasting POW" should result in a transaction that gets me a place in the queue, but only one of these made it into my account history.
Edit: sometimes you just have to complain to make it work I guess...Code: [Select]2016-04-03 17:55:16.269806500 3316269ms th_a witness.cpp:436 operator() ] Broadcasting Proof of Work for cyrano
Nevertheless, this only proves my assumption that for every "Broadcasting POW" message there should be one TX in my account history, but there isn't.
2 285428 4a49bdf267c686f76b2558cf6ac3807eb1373e62 pow {"worker_account":"cyrano", ...
@thereverseflash I created a node : "122.114.47.242"But I haven't a private key ,so I can't create a account.privete key is bitcoin's
I got a publick key :STM5p78kHbL33Rn3JWkTWRE2B9uz6gy4r1KbfAKLNQGE3ovMBS5bu
Any one give me some coins?
I don't known how to create my first account
./steemd --miner='["accountname","${WIFPRIVATEKEY}"]' --witness='"accountname"'
get_account mottler
create_account_with_private_key
create_account( string creator, string new_account_name, string json_meta, bool broadcast )