 Show Posts
|
|
Pages: [1]
|
WTB Vested accounts. 30M+ Vests. Serious inquiries only.
I guess the price would be no more than 10BTC I am looking to buy not sell. I was speculating. |
|
|
|
WTB Vested accounts. 30M+ Vests. Serious inquiries only.
I guess the price would be no more than 10BTC |
|
|
|
I am just a tad bit jaded also because he knows I am working on JAMBOX a decentralized social networking and then he goes and throws his efforts to promote Steemit. And especially after he had basically talked me out of thinking that Bitshares might be a credible team to partner with. I had in 2015 thought about maybe my best direction was to start talking with Bitshares and in fact I did make one post over there offering to implement my Zero Knowledge Transactions for them. But that is okay. I love the competition. Gives me even more motivation.
Ya know if anonymity was really the #1 market, I would have built a coin on my Zero Knowledge Transactions. But I realized it wasn't the good priority. There is no significant adoption, so it ends up just being a fist fight between the various camps, because no camp can really go gain an adoption market to make it clear which one is the winner.
@iamnotback I think Dan and the team will be more than happy if your Zero Knowledge Transactions could be implemented in Steem. Looks like Steem now has enough funding, so you can get what you want if the work is well done. Thoughts? |
|
|
|
have somewhat a naive question, or three rather
1. did POW which rewarded miners with STEEM ended ?
Yes that was only during the pure PoW phase. 2. if true to the above, can current POW that rewards miners with VEST be converted to STEEM ? Yes but conversions are only 1/104 per week. It is probably best to mine to increase your Steam power (formerly known as VESTS) if you intend to use the system. But you can mine, convert, and sell if you really want to. Alternatively you can sell the whole account with Steem Power inside, just like someone posted above. |
|
|
|
420 million VESTS
party time
edit: 420 billion VESTS....maths are hard
what do you mean?  ok this is crazy. thanks a lot A few days ago every 1 VESTS got split to 1M VESTS. |
|
|
|
On which block STEEM switches from DPOW to DPOS? And what is estimated time of this swich? Or target spacing between blocks?
Block 864000. Around 2016-04-24 05:40 UTC The switch should be instantly. Block 864000 is coming later than estimated because some miners are not producing. |
|
|
|
On which block STEEM switches from DPOW to DPOS? And what is estimated time of this swich? Or target spacing between blocks?
Block 864000. Around 2016-04-24 05:40 UTC The switch should be instantly. |
|
|
|
Any pool for this coin?
It's supposed/designed to be anti-pooling. If I type get_miner_queue in the cli_wallet, and none of my miners show up.....does this mean something is wrong?
Not necessarily,but there is a problem with network all seednodes are down again. FYI usable seed node list: seed-node = 104.199.157.70:2001
seed-node = 104.236.82.250:2001
seed-node = 162.213.199.171:34191
seed-node = 192.99.4.226:2001
seed-node = 46.252.27.1:1337
seed-node = 81.89.101.133:2001
seed-node = 52.4.250.181:39705
seed-node = 85.214.65.220:2001
seed-node = seed.steemed.net:2001
seed-node = steem.clawmap.com:2001
seed-node = seed.steemwitness.com:2001
seed-node = steem-seed1.abit-more.com:2001
|
|
|
|
too late to release alpha GUI, big part of steem already mined with low difficulty and few persons holding steem supply, now the train moved away..........so i think no one will interest to mine steem. With current rate and hashing power, an AWS 36 core VPS can earn ~0.2 BTC per day. Perhaps you have no interest in such a low profit. |
|
|
|
The incentive to hold VESTS will fall dramatically over the next few weeks as the rate of change in the supply of STEEM falls.
Do you mean the incentive to hold VESTS or the incentive to create new VESTS from STEEM?Bump Maybe both? In short, current conversion ratio is about 27:1, and the ratio is increasing by about 2:1 4:1 2.6:1 everyday. So the % speed of ratio increasing is decreasing, thus less incentives to convert STEEMs to VESTS. 6 days passed, current ratio is 41:1. On average 2.3:1 increment per day. It's a bit less than linear. |
|
|
|
https://steem.herokuapp.com is not working right now. Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.
|
|
|
|
|
I'm really sorry for shutdown the network..
|
|
|
|
* Users not in the ACTIVE witness set should not have to worry about their
* key getting compromised and being used to produced multiple blocks so
* the attacker can report it and steel their vesting steem.
*
* The result of the operation is to transfer the full VESTING STEEM balance
* of the block producer to the reporter.
Does it mean it is theoretically possible for the users who ARE in the active witness set, should worry about their key getting compromised and being used to double-produce blocks, so all their VESTING STEEM balance could be transferred to the malicious reporter? I mean is such kind of attack still possible? You should guard your block producing keys like your balance keys. It is no different than someone having their bitcoin wallet key compromised and allowing the attacker to drain your account. This is how we prevent the nothing-at-stake attack and the "produce on multiple forks" attack. Conclusion: don't try to setup/run a backup node with same signing key. Witness is a high risk job  |
|
|
|
The incentive to hold VESTS will fall dramatically over the next few weeks as the rate of change in the supply of STEEM falls.
Do you mean the incentive to hold VESTS or the incentive to create new VESTS from STEEM?Bump Maybe both? In short, current conversion ratio is about 27:1, and the ratio is increasing by about 2:1 4:1 2.6:1 everyday. So the % speed of ratio increasing is decreasing, thus less incentives to convert STEEMs to VESTS. Analysis: Conversion ratio = STEEM : VESTS = TOTAL_VESTING_FUND_STEEM : TOTAL_VESTS Every block, when the miner/witness got 1 STEEM as reward, 2 STEEMs are added to TOTAL_REWARD_FUND_STEEM, and 27 STEEM are added to TOTAL_VESTING_FUND_STEEM Because block interval is almost constant, everyday ~28800 blocks are produced, so 28800 new STEEMs to miners and ~778k STEEMs to TOTAL_VESTING_FUND_STEEM. The ratio keeps increasing due to TOTAL_VESTING_FUND_STEEM keeps increasing. * the speed of ratio increasing is linear if nobody deposit to VESTS or withdraw from VESTS. With current ~405K total VESTS, the ratio will increase by 778K:405K ~= 1.92 : 1 everyday. * if every miner convert new STEEMs to VESTS, TOTAL_VESTING_FUND_STEEM will increase by STEEMs, TOTAL_VESTS will increase by (STEEMs / ratio), it's ~1066 VESTS with current rate, the speed of ratio increasing will be a little lower (about 0.005 : 1 with current supply). * if every VESTS holders started converting VESTS to STEEMs, on average everyday 1 / (7 * 52 * 2) of VESTS will be converted, with current 405K supply, it's ~556 VESTS, so the speed of ratio increasing will be a little higher (about 0.003 : 1 with current supply). //Update: Due to POW reward, the daily inflation should be doubled, so 28800*2 to miners and about 4:1 of daily ratio increasing.
//Update2: POW reward doesn't add to TOTAL_REWARD_FUND_STEEM at same time, so still 28800 * 2 to miners, but only 28800 * (2 + 2) * 9 to VESTS, so 1.15M of total daily inflation, about 2.6:1 of daily ratio increasing. |
|
|
|
is it ok to use the same WIF key for few mining accounts?
and to use the same accountname in --witness and --miner ?
1. only use --witness on one machine or you will double produce blocks and lose your account 2. you can use the same key so long as you mine on the same computer in the same process By "lose" and account, does that mean you lose the ability to mine with it or the balance too? How can you know which accounts are "lost"? By "double producing" the nodes are making forks. I wonder how the account will get "lost" as well.. In order to ban an account, nodes (at least block producers) on the major (longest) chain need to know things happened on a minor chain (at least who was forking), then refuses any transaction signed by that account. If this is the case, the "bad one" will lose everything, STEEMS, VESTS, account name etc. I don't know how to automate this right now, since forking can be caused by accident, IMO it's hard to identify automatically & accurately. On the other hand, it could be easier to be identified manually, although still need some efforts. Then comes another question: how to convince the producers to ban an account. In the mining phrase, if enough hashing power is making forks, it will be troublesome. In the voting phrase, the major VESTS holders (atm it's steemit) decide the block produces, so it's possible for them to do anything. Just thinking out loud.. |
|
|
|
is it ok to use the same WIF key for few mining accounts?
and to use the same accountname in --witness and --miner ?
1. only use --witness on one machine or you will double produce blocks and lose your account 2. you can use the same key so long as you mine on the same computer in the same process I don't understand what the above is supposed to mean. You have to set --witness only on one machine, but you can only mine with the same key on the same computer in the same process? Then what's the point? Doesn't this mean that you have to use a different key + witness for every "miner" that is setup? So wouldn't that make setting up a miner without the --witness option completely useless? If not, how is one supposed to configure multiple miners on a single witness-account? In STEEM chain, blocks are produced by witnesses. Which block should be produced by which witness, is calculated at the start of each 'round' (every 21 blocks), as a consensus by every node. By specifying --witness plus a key (which is in --miner), the node will produce blocks with that witness. So if two machines have same witness and key, both of them will produce a block when it's the witness's turn. This is the so-called "double produce". By specifying --miner but no --witness, the node will only mine with that miner but won't produce blocks. So it's possible to have multiple processes/hardware work for one witness. So what's the use case? Assume there are 100 machines, each machine has the hashing power to keep 1 'ticket' in the queue, what's the easiest way to setup them? Probably run one server with --witness and --miner (specify 100 times with 100 different accounts), and other 99 servers with --miner and no --witness (with all 100 accounts as well). Or maybe even better if use more accounts. //Update: It's possible to specify --witness & --private-key but no --miner, so the node will produce blocks only, but won't mine. In this way an elected witness won't get voted out by itself when accidentally mined out a ticket. //Update2: Theoretically it would be somehow inefficient if use same key on different machines. |
|
|
|
Hello, this is abit from BitSharesTalk. Due to helped revive BitShares network twice, my witness "in.abit" on BitShares network has the lowest block missing rate, far below average (see https://bitshares.org/wallet/#/explorer/witnesses, click Explore -> witnesses if see a login page). I'm interested in running a witness in Steem when the DPOS phase comes. I fixed a few bugs inside Graphene code base recently, am currently working on building features for BitShares by expanding Graphene code base, perhaps I can help with developing Steem some day. |
|
|
|
|
.. 
