Pages:
Author

Topic: [ANN][STEEM][POW] - An experimental Proof of Work blockchain - page 2. (Read 10436 times)

newbie
Activity: 46
Merit: 0

when is block to halving? 4 year like bitcoin?
member
Activity: 98
Merit: 10
NO PREMINE | NO INSTAMINE this is not true and should be removed  Angry launch of this coin was setup to let dev instamine and get big premine...

This is true. The coin is so impossible to mine that you can't say it wasn't a premine/instamine.

Dev: what do you plan on doing with the premine?

You need to start by saying what safeguards you will make against dumping it.

And don't delete this post. I'm not criticizing what you did. I want to know your plans.
legendary
Activity: 2576
Merit: 1073
Current account list:
Code:
[
  "aaron",
  "abit",
  "acp",
  "adamstgbit",
  "alice",
  "alice1",
  "almond",
  "amph",
  "amy",
  "ander",
  "andrew",
  "apple",
  "arthur",
  "balthazar",
  "barbara",
  "batel",
  "batel1",
  "batel2",
  "batel3",
  "ben",
  "billgates",
  "bitchipper",
  "bitcoin",
  "bitcoinkkk",
  "bitshares",
  "bnrtx",
  "bob",
  "bobby",
  "boltz",
  "brian",
  "bryan",
  "carl",
  "charles",
  "chartbuddy",
  "chris",
  "cisahasa",
  "cloop",
  "cloop1",
  "cloop2",
  "coins4lunch",
  "cypherdoc",
  "dan",
  "daniel",
  "dannac",
  "dantheman",
  "dantheman1",
  "dantheman2",
  "dark",
  "david",
  "dealthandtaxes",
  "devshuster",
  "dnotes",
  "doesntmatter",
  "donald",
  "donna",
  "dorthy",
  "drays",
  "drpd",
  "elizabeth",
  "eric",
  "ernest",
  "ethereum",
  "facebook",
  "faddy",
  "faddy1",
  "faddy2",
  "faddy3",
  "faddy4",
  "frank",
  "fuck",
  "gary",
  "griffith",
  "helen",
  "hello",
  "hilariousandco",
  "howard",
  "initminer",
  "initminer18882",
  "insurance",
  "james",
  "jandbzan",
  "jason",
  "jeff",
  "jeffrey",
  "jennifer",
  "jeremy",
  "john",
  "jose",
  "joseph",
  "kevin",
  "kointrend",
  "kprell40",
  "larry",
  "laura",
  "leigh2k14",
  "linda",
  "liondani",
  "localhost",
  "luis",
  "malekbaba",
  "mangox",
  "margaret",
  "maria",
  "mark",
  "messi",
  "miners",
  "mn12defgj1",
  "mottler",
  "mottler-1",
  "mottler-2",
  "mottler-3",
  "mottler-4",
  "mottler-5",
  "mottler-6",
  "mr11acdee",
  "mr11acdee1",
  "mr11acdee2",
  "mr11acdee3",
  "null",
  "nxt",
  "nxt1",
  "nxt2",
  "temp",
  "thisisnice",
  "thisisnice0",
  "thisisnice11",
  "thisisnice2"
]

I have verified that anyone with a 1 year old i7 CPU can start it up and start producing blocks in under an hour.  

That's weird. I see the name of my account in this list above (drays), but I am not mining this and never even tried  Huh

Just opened the thread and reading. Not even sure why someone would have used my nick? It is not a common word or common name at all. Also I see several nicks of other hero members of BCT, but none of them even posted in this thread, so I doubt they participate in any way.

Now - I would have considered mining this, if I were at my PC at the moment Smiley, but the fact is - I didn't mine it!
So how my nick appeared in the list?
Any explanation to this, Dev?

Welcome drays, if you would like to have that account I will gladly transfer it to you.   I reserved many accounts from bitcoin talk to keep them available for you.  

OK then, got it. Interesting idea to bring in new people though Smiley
It looks like there are a lot of interesting and nonstandard ideas here, but I have to postpone the investigation for now.. The time is really inconvenient for mining or investigating the code, as its time to sleep here... Smiley

Wish a good luck to you. Its not often I tell it here on forum, but I'm a somewhat intrigued by all this nonstandard approaches. Its always nice to see someone trying to bring in some fresh air, and to experiment a bit.
sr. member
Activity: 450
Merit: 250
NO PREMINE | NO INSTAMINE this is not true and should be removed  Angry launch of this coin was setup to let dev instamine and get big premine...
full member
Activity: 209
Merit: 100
Smiley If you study the code you will discover that this chain has 6 different kinds of proof of work, most of them much more useful than spinning a CPU.


I don't see it? Seems like one kind of proof of work... I think you misunderstand what 'multi-algo' is. I suggest you check the Myriad website for more info at myriadcoin.org.

Your Proof of Work could be likened to 6 'rounds of hashing', similar to X11, but as you say, the rounds are more 'useful'.

Multi-algo is a different beast entirely. You have 5 actual different proof of works. Each has its own independent difficulty and finds a share of the blocks (share determined by individual target blocktimes for each PoW).

I am familiar with multi-algorithm POW.  The POW in this is accessible to far more people than anything before it.


I don't understand how. I'm not saying STEEM PoW is without merit— but if you're limiting blocks to the top 21 miners, how is it 'accessible to far more people than anything before'?
member
Activity: 70
Merit: 10
I'll be able to change everything!
Smiley If you study the code you will discover that this chain has 6 different kinds of proof of work, most of them much more useful than spinning a CPU.


I don't see it? Seems like one kind of proof of work... I think you misunderstand what 'multi-algo' is. I suggest you check the Myriad website for more info at myriadcoin.org.

Your Proof of Work could be likened to 6 'rounds of hashing', similar to X11, but as you say, the rounds are more 'useful'.

Multi-algo is a different beast entirely. You have 5 actual different proof of works. Each has its own independent difficulty and finds a share of the blocks (share determined by individual target blocktimes for each PoW).

I am familiar with multi-algorithm POW.  The POW in this is accessible to far more people than anything before it.
full member
Activity: 209
Merit: 100
Smiley If you study the code you will discover that this chain has 6 different kinds of proof of work, most of them much more useful than spinning a CPU.


I don't see it? Seems like one kind of proof of work... I think you misunderstand what 'multi-algo' is. I suggest you check the Myriad website for more info at myriadcoin.org.

Your Proof of Work could be likened to 6 'rounds of hashing', similar to X11, but as you say, the rounds are more 'useful'.

Multi-algo is a different beast entirely. You have 5 actual different proof of works. Each has its own independent difficulty and finds a share of the blocks (share determined by individual target blocktimes for each PoW).
member
Activity: 70
Merit: 10
I'll be able to change everything!
Thread is all dev talking to himself from different accounts and erasing anyone thats not hims posts  Grin


funny shit

If only it were true. The real irony is that despite looking like a sock puppet it isn't me Sad 
legendary
Activity: 963
Merit: 1002
Thread is all dev talking to himself from different accounts and erasing anyone thats not hims posts  Grin


funny shit
member
Activity: 70
Merit: 10
I'll be able to change everything!
Smiley If you study the code you will discover that this chain has 6 different kinds of proof of work, most of them much more useful than spinning a CPU.
member
Activity: 70
Merit: 10
I'll be able to change everything!
legendary
Activity: 2576
Merit: 1073
full member
Activity: 209
Merit: 100
This is a very interesting idea. I love the pool resistance, but it feel like 21 miners is too limited, at least in the beginning of the coin's life.... Would have been more interesting if this coin was multi-algo (simultaneous proofs of work). Then it would be pool resistant, and somewhat mining farm resistant. It would allow for more top miners as well. For instance:

sha256 (k)
scrypt (k)
groestl (k)
skein (k)
qubit (k)

Thoughts?
member
Activity: 83
Merit: 10
i've made my first tx :

Code:
{
  "ref_block_num": 20616,
  "ref_block_prefix": 1419248958,
  "expiration": "2016-03-23T23:48:27",
  "operations": [[
      "transfer",{
        "from": "****",
        "to": "*****",
        "amount": "1.5 1.5",
        "memo": "test"
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "******640a437ff373e886115776f15ab707ceb4597f6ff772231225****..........."
  ]
}

but cant verify if received, the "to" account balance didn't change.

transfer FROM TO AMOUNT memo bool << what is bool ? i put 1 in there but not sure  Undecided

EDIT: i found out the bool = broadcast the tx true or false

but then it fails , im not sure what is the allowed amount and whats the format ? 1.5, 1.000 and 1 do not work .


transfer fromname toname "1.000 STEEM" "memo" true

It is important to have the full precision 1.000 and to use the quotes.

now it works  Grin im enjoying with steem

Thanks
legendary
Activity: 1131
Merit: 1007
Anyone able to create some step by step instructions with which an uneducated plebeian such as myself may participate in mining some STEEM  Grin
member
Activity: 70
Merit: 10
I'll be able to change everything!
i've made my first tx :

Code:
{
  "ref_block_num": 20616,
  "ref_block_prefix": 1419248958,
  "expiration": "2016-03-23T23:48:27",
  "operations": [[
      "transfer",{
        "from": "****",
        "to": "*****",
        "amount": "1.5 1.5",
        "memo": "test"
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "******640a437ff373e886115776f15ab707ceb4597f6ff772231225****..........."
  ]
}

but cant verify if received, the "to" account balance didn't change.

transfer FROM TO AMOUNT memo bool << what is bool ? i put 1 in there but not sure  Undecided

EDIT: i found out the bool = broadcast the tx true or false

but then it fails , im not sure what is the allowed amount and whats the format ? 1.5, 1.000 and 1 do not work .


transfer fromname toname "1.000 STEEM" "memo" true

It is important to have the full precision 1.000 and to use the quotes.
member
Activity: 83
Merit: 10
reading the code, seems like we will have a decentralized exchange or something like that.
Code:
 /**
    * This operation creates a limit order and matches it against existing open orders.
    */
   struct limit_order_create_operation : public base_operation
   {
      string           owner;
      uint32_t         orderid = 0; /// an ID assigned by owner, must be unique
      asset            amount_to_sell;
      asset            min_to_receive;
      bool             fill_or_kill = false;
      time_point_sec   expiration = time_point_sec::maximum();

      void  validate()const;
      void  get_required_active_authorities( flat_set& a )const{ a.insert(owner); }

      price           get_price()const { return amount_to_sell / min_to_receive; }

      pair get_market()const
      {
         return amount_to_sell.symbol < min_to_receive.symbol ?
                std::make_pair(amount_to_sell.symbol, min_to_receive.symbol) :
                std::make_pair(min_to_receive.symbol, amount_to_sell.symbol);
      }
   };
member
Activity: 83
Merit: 10
i've made my first tx :

Code:
{
  "ref_block_num": 20616,
  "ref_block_prefix": 1419248958,
  "expiration": "2016-03-23T23:48:27",
  "operations": [[
      "transfer",{
        "from": "****",
        "to": "*****",
        "amount": "1.5 1.5",
        "memo": "test"
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "******640a437ff373e886115776f15ab707ceb4597f6ff772231225****..........."
  ]
}

but cant verify if received, the "to" account balance didn't change.

transfer FROM TO AMOUNT memo bool << what is bool ? i put 1 in there but not sure  Undecided

EDIT: i found out the bool = broadcast the tx true or false

but then it fails , im not sure what is the allowed amount and whats the format ? 1.5, 1.000 and 1 do not work .
member
Activity: 83
Merit: 10
Code:
transfer(string, string, steemit::chain::asset, string, bool)

can we use account names on from & to ? or only public-keys?
member
Activity: 70
Merit: 10
I'll be able to change everything!
how do we get total network hash rate & current diff ?

Code:
./cli_wallet 
>>> info
{
  "id": "2.0.0",
  "head_block_number": 19654,
  "head_block_id": "00004cc66d03e9cf75fbdde0671dd529c7860dd5",
  "time": "2016-03-23T22:58:45",
  "current_witness": "brian",
  "total_pow": "18446744046983894345",
  "num_pow_witnesses": 84,
  "virtual_supply": "79857.000 STEEM",
  "current_supply": "79857.000 STEEM",
  "confidential_supply": "0.000 STEEM",
  "current_sbd_supply": "0.000 SBD",
  "confidential_sbd_supply": "0.000 SBD",
  "total_vesting_fund_steem": "242.000 STEEM",
  "total_vesting_shares": "242.000000 VESTS",
  "total_reward_fund_steem": "39308.000 STEEM",
  "total_reward_shares2": "0",
  "sbd_interest_rate": 1000,
  "average_block_size": 115,
  "maximum_block_size": 131072,
  "current_aslot": 27575,
  "recent_slots_filled": "340282366920938463463374607431768211455",
  "last_irreversible_block_num": 19633,
  "max_virtual_bandwidth": "1379246476653931178",
  "current_reserve_ratio": 983,
  "head_block_num": 19654,
  "head_block_age": "0 second old",
  "participation": "100.00000000000000000",
  "median_sbd_price": {
    "base": "0.000 STEEM",
    "quote": "0.000 STEEM"
  }
}

num_pow_witnesses => total in queue.
LZ = num_pow_witnesses/4 + 4
On average 1 POW is found every 63 seconds.

HR = (2^25)/63  or  532,610 HPS

A shortcut estimate is num_pow_witnesses.   

My math could be wrong, but it looks close.
Pages:
Jump to: