[ANN][STEEM][POW] - NO IPO | NO PREMINE | NO INSTAMINE (relaunch)

[thereverseflash]

how to send STEEM to openledger-wallet ?

tried to send 10 coins to "openledger" with memo open.steem:myopenledgeraccount

Automated deposit and withdraw is not fully operational.  It could be a week until it is properly automated. Things are still in the testing phase so expect delays until it comes online.

[kahir]

thereverseflash

still no gui windows wallet .......

[Jookly]

I checked my miner today and I think I was getting the same fork issue.  I restarted the miner so hopefully that will fix it.  Not quite sure yet.

[puppies]

I checked my miner today and I think I was getting the same fork issue.  I restarted the miner so hopefully that will fix it.  Not quite sure yet.

If it doesn't try to launch it with the --resync-blockchain flag.  You will have to redownload the chain, but the fork should resolve.  It did on my forked nodes.

[JoeyD]

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?

[SalimNagamato]

created a Dockerfile + build instructions for anyone interested to run steemd in a docker container
https://github.com/blood2/steemd-docker
also helpful if someone is able to run Ubuntu and Docker, but still having trouble with build
if i make a mistake please let me know. tested it on my VM

[steemit]

dev talking about steem:

https://soundcloud.com/beyond-bitcoin-hangouts/e147#t=48:30

[copychicken]

where did you get private key?

nvm I got it
[/quote]

where exactly?

[copychicken]

The wif key must be random, or it has to do with the public key generated when we launch the wallet?

[copychicken]

and what directory is the config.ini?? i cant seem to find it anywhere.

[STEEMD]

and what directory is the config.ini?? i cant seem to find it anywhere.

this folder wont show if you didnt start ./steemd for the first time.

/steem/programs/steemd/witness_node_data_dir

[abitmore]

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.

[copychicken]

haha i still have problems for one pc, and you are talking about 100?

on the mining.. should i have 2 instances of the wallet open?

one with the mining command, and the other with rpc endpoint?

[copychicken]

This is what i am getting now.

[Mysterion]

So,

I get your point, you wanna have a majority share in your own coin that you put so much work in. Understandable.

However you'll have a very hard time to shake the scam image. That's not saying your coin won't land on a good exchange or do ok, but anyone looking at STEEM will see it as a pump and dump opportunity and you'll have a hard time building a real community for it since you'll be ruined by day traders that know how to handle your coin.

I guess my question is why not make it a legit launch with a premine or ICO and disclaim all the great features from the start?

[seedtrue]

This is what i am getting now.

You just showed us your private key...or most of it at least. When you get things working do not use that key for security reasons.

[Grandpa Jones]

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"?

[copychicken]

This is what i am getting now.

You just showed us your private key...or most of it at least. When you get things working do not use that key for security reasons.

yes i know but as soon as i get it to work, i will change it.

[abitmore]

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

[tombstone2]

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