Fixed via discord it would seem

Ok. I'm not aware of the procedure / status. hclivess is the one handling that.

If you go back a little, there is a specific thread linked for testnet rewards, I think it's better to ask directly there.

Sure. Risers are only needed if it does not fit in the regular pci-e slots.

Well, this metric is only useful for the currency use case I think.
Some coins are specifically targeting a huge tx throughput.
This is not an ultimate goal.
For Bismuth, see point 7 https://steemit.com/cryptocurrency/@aetsen/bismuth-developer-interview-hclivess
(but Having an insane amount of tx per second is not a current bismuth goal)

What's more interesting is why you would need a huge tx throughput.
apart for mainstream currency use (which is just one small use case for a blockchain platform), this is not a real concern, at least atm.

If what you want before all (but you'll have to tell why, because it will come at the expanse of other metrics, or safety, or decentralization, or features) is a huge tx throughput,
then blockchains are not the best fit. Look into DAG instead.

As far as Bismuth is concerned, the core thing is that it's not built upon an existing protocol/platform with fixed limits.
Bismuth is a new protocol/platform, from scratch, evolving.
And it's evolving fast, with priorities shifting fast ,also.
What I mean, is that atm, tx throughput is not an issue, far from that.
So this is not a current dev priority and the metric makes no sense: it's more than the current usage requires, so the real metric is irrelevant.
IF (and only IF) it becomes an issue, then the team has many ways to answer the problems, and they will come quick.
Some work already is done, or under work, to reduce tx related bandwidth usage for instance.

Then, wait until you see what we have in our bag for Masternodes technology.
This tech could be used way further to offload a lot of tx, storage, bandwidth from the main chain, and that, will be a real game changer, way more than a single metric.

pci bus is for power only, fpga communicates over usb

Can you be more precise?
What is your use case, what scale are you refering to?

Dapps based upon a chain (not just Bismuth one) use on chain transactions to operate.
Bismuth Dapps are based upon transactions and "openfield" data. That is, an optional arbitrary data field that can be used for virtually anything.

Any operation is then a Bismuth transaction.
Bismuth transaction have a fixed base fee plus a variable part that depends on the data field length.

So, yes, any Dapp will consume Bis as part of its working.
It's how all Dapps on any blockchain work.

The chain provides a secure infrastructure, the dapps build upon and "pay" for that.
Then the transaction fees go to the miners, who are the one securing the infrastructure via PoW.

Hi,


See
https://docs.google.com/spreadsheets/d/1--SNuCPBRblrlhSbU6QNoE-Hwkw1GWvnggvV633P92g/edit#gid=937505860


None, because of the custom message needed (cryptopia, heat nodes) or manual validation process (octaex)

Check you didn't paste an extra character, or capitalized the first char, or forgot some.

Well, I have to disagree. Hashrate is constant, depends on the gpu and settings only, does not depend on luck. So it's a stable metric for the miner software, when calculated in a fair way.
How is it weird to report what the miner effectively computes? Every fair miner does that.
On the pool side, found shares are what counts, and this metrics is shown on the pool, with historical graphs for each miner address.

So, I don't get the "transparent" thing. I do report both accurate hash from the miner and accurate shares from the pool.
All data is there, raw, for everyone. It's not on others.


So, here you're talking luck and variance.
Yes, there is a large variance from round to round (1 round = 1 hour).

This variance is caused by 2 things :
- network variance (I added the graph of the net variance on the dashboard a few weeks ago). When netdiff varies, so do the blocks per hours for the whole net.
- your personal variance. The more hash you have, the less variance you'll experience. On average, you may be unlucky on some rounds, but then more lucky than average on others. On average, everyone luck is the same, so in the long run you can't loose every time.

I do agree that
- Lowering pool diff
- having rounds longer than 1 hour
would make the luck factor less visible.
I may lower the pool diff later on, but my priority it to have a stable and reliable pool, and I have somehow to adjust to the global net hashrate and to the average miner hash.
So yes, small miners see the luck factor more. But on average, it's the same.

I do not see a transparency issue there. The shares are what they are, I report what the miner sends, I can't influence your miner on sending less shares on a good round .
pool shows graphs and share counts, miner has logs with found shares, all is transparent. Some others pools do not even provide that data.
I think I'm the pool providing the most data.
On the other pool, you don't even have the historical data to compare and see your luck from hour to hour...


I could, but this is no transparency issue. Pool fees are displayed on the pool website.
They are not on the one you say is "most transparent".


Bis-pool miner may indeed be better suited for Amds and computes the hashrate in the miner the same way, so can be compared to EggPool.
The other one does not compute the hash rate in the same way, so the hashrate improvement you saw is not a real one. You were not comparing the same metric.
(Not a transparency issue neither from Eggpool: I say how the hashrate is computed - number of tested solutions per second - coinsaurus computes a different thing and does not say what nor how)


So, I do understand your concerns, mainly Amd efficiency and variance because of low hash.
I get it that another pool may give better results for your case (but do your tests again, I'm 100% sure it's not the one you believe it is) and that's ok with me.

Honestly, I just don't get the lack of transparency you hold against EggPool , and why you say the other pool, the most opaque one, is the "most transparent".

Thanks for the review!

I'd like to point a few things:

This is no more accurate. Coinsaurus now publicly admits to have 8% fees built in the miner, via randomly diverted shares.
Those were not accusation by the other pools, but facts checked by the bismuth team.


Agreed.
Your tests may not reflect the current state of the pools rentability. Don't take a single test, done at different times, as a stable comparison.
If you really compare again, you'll see that your results now will be very very different from what you report.


Also, what do you mean by "most transparent"? What is not transparent in Eggpool, what could I improve?

Ok, so you're mining with a single gpu and do other things at the same time.
Egg miner's goal is to give maximum performance and pushes the hardware. It's purpose is to mine on a dedicated rig, not to let the gpu rest.

By comparing, I meant comparing the rewards, not the displayed hash rate.
Won't argue on that here, the subject has been covered extensively on the discord a while ago.
idk why this pool decided to, but the two hash rates it calculates and displays (on miner and on pool, 2 different values) both have nothing to do with the real hash other pools are computing from the gpu miner itself, so it really can't be compared.

As for the lags, with a single gpu there's no reason it acts that way. Happy to help on discord if needed.

Renegade1979:
Eggpool payout is 10 by default (so you pay less tx fees) but can be lowered to 1 BIS on simple request.
Miner lag experience is very subjective then. Egg miners say the opposite: lag under windows disappeared with latest version a few weeks ago, coinsaurus still lags.
As far as rentability goes, just compare and you will see which one pays more. (Hint: it's not coinsaurus, by a long shot)

Crypomad08:
Did you try moving the wallet to the garage, too?
Joke apart, the pool you mine on should have a dashboard with your shares, pending payouts and such.
Check this dashboard first, and if you have a question, head to the matching pool channel on discord : https://discord.gg/5Kn3zD4
But in any case, you'll have to trigger a minimum 1BIS balance and then payout time.

Some examples you may find via the "projects" pages on bismuth.cz website.
(several native example dapp inside)

Also check those repos with doc and apps:

Native API doc
https://github.com/EggPool/BismuthAPI

Json-rpc
https://github.com/EggPool/BismuthRPC

sample PoC of event sourcing:
https://github.com/EggPool/BismuthEvents

Ask me on the discord @eggdrasyl or github @eggpool if you need something.

The official link for the third party web wallet was removed from the ann, that's all. Afaik, the web wallet itself is still there and you can move your funds out if wanted.

API documentation and related info could be a good start.
https://github.com/EggPool/BismuthAPI

To clarify the MN approach:

- MN will still need Bis collateral and rewards will be paid in BIS
- A technical paper with strategy and details will come later, it's too soon right now
- A PoS chain, as a second level, will allow MN to reach consensus independently from the Bis PoW chain.
- Nothing will change for Bis, Users or miners. Bis and balances will stay on PoW chain.
- The two levels operating on two different strategies allow to highly strengthen and secure the network, since an attack would have to forge 2 chains with very different triggers.

So the MN implementation will not just be a "ping" test like on some coins, but would embed, from the start, innovative and secure algorithms.
All this is being evaluated, coded, documented, tested by the team.

Hi,

Owner of EggPool Here.
I'm not used to talk or watch over here, but you'll find me at bismuth's slack and discord.

Since I see some questions about the pool fees, let me give some perspective on the why.

When I launched the pool and the gpu miner, Bismuth was being raped by a few private solo gpu miners.
I spent a month coding a pool and miner from scratch. really from scratch, all of it.
It's not some clone like other coins, where you drop some files on a vps and use an existing miner.
All is custom, from scratch.

Why such fees?
- because I'm dedicated 24/7 to this project, Bismuth and Eggpool
- because the fees cover the pool, but also the miner. It could be 5% pool + 5% miner fees.
- I do a spent a huge amount of time supporting users. Join slack or discord, you'll have answers. You won't have to run after me for days.
- superior infrastructure: it's not some cheap vps. I do run several Bismuth nodes, supporting the net with stable nodes, and I have designed a distributed pool architecture, with a central dashboard. I operate from several dedicated servers, in different parts of the world. A pool can crash or be under maintenance, you continue to mine. Check for historical pool downtime, you won't find. I did plan for long term reliable operations, not some quick cash.
- R&D. Lots of R&D goes into the miner. It's far superior to the open source solo miner. Lately, I sold some bis, I have to admit, so I could buy a 1080Ti for tuning purposes. Before that I bought an AMD Gpu so I could do specific optis for AMDs.
- Look, last update of the miner alone gave the miners +15 to +20% more hashrate. So, even with the 10% fees deducted, miners still get 5% more!!!!

I could have lowered to 5% fees, let the miner as it was, and everyone would have lost.
I'm really trying my best, both for bismuth - not all pools or solo miners are dev team friendly - and you miners: support and updating miner, reliable distributed pool, so everyone can win more. I don't do this as a side project, I'm heavily involved.

Don't look at what fees I "take", it's of no use: you do have the choice to pick another pool or mine solo, or dev your own pool and miner. I did it, you can too!
(See, I even help wanna be bismuth pools for the technical side)
If you mine on Egg, it's because you get more (even with the fees deducted) than you would the other way.

In the end, YOU get more. Isn't that what counts?

And moreover, you're supporting a dev friendly pool, that helps and stabilize the bismuth network long term.

If I dropped my fees today, that would only mean less support, less dev, a higher netdiff maybe, and a few more coins dumped by the miners. Would that really help?

Hi there,

Newbie here, but I'm involved in Bismuth since a while
As a miner, it is still very profitable to mine.
Bismuth is very promising: first full python blockchain, written from scratch, with innovative features and a nice dev team.
I learnt a lot about crypto by just reading the $BIS code.

As a pool owner (EggPool.Net) : I spent a lot of time building a solid infrastructure and developing custom code to get a reliable pool.
Several servers around the world, several pools : no single point of failure.
A custom protocol that ensures efficient mining, thus finding more blocks.
A custom optimized GPU miner, AMD and NVIDIA, LINUX and WINDOWS.
610+ MH/S for stock RX580, 1800/1900+ for a 1080Ti.