Running Bitok - 0.3.19 Mainnet

[yoshikiazuma]

Personally, I really like the new look. The old explorer is definitely OG, but this new one has a real soul to it. The functionality actually got even better, and the new theme reflects the current state of the project really well. Honestly, seeing this level of work, it’s hard to believe elvisjedusor is pulling this off alone  

"Has a real soul to it" - that's exactly what Im thinking.

We need to move from just the "Satoshi's Legacy" concept to the "Satoshi's Programmable Money" concept, since that's what we really are. Because thats what he originally put into Bitcoin. And now, 15 years later we've activated what had been hidden for so many years. In that sense, the new explorer really hits the mark.

Yes (: it's more of a cypherpunk vibe which I like the new explorer

Yet the UraniumX pools don't require the special parameters to mine.

Pool can abstract some parameters internally. But this is technically a bad idea in crypto.

1. It breaks transparency
When you explicitly pass params in miner you know exactly what hash function executing. If the pool injects parameters internally, you rely on the pool operator’s correctness and lose verifiability at the miner layer.

2. Multicoin proxy abuse
A generic yespower miner could be pointed to multiple coins. Pool can silently redirect hashing between chains. And yes, rented hash services can adapt more easily.

3. Share Validation
If miners configure params, invalid shares are rejected at miner level. Misconfigured miners fail fast. But if pools inject parameters, miner could compute wrong variant hashes.

It looks like some other mining SW used prepend (ALGO -a) minerd.exe -a yespowerurx -o stratum+tcp://cpu-pool.com:63378 -u [WalletAddress] to designate the specific ALGO rather than adding the special parameters to the miner

Any mining soft (cpuminer, etc.) can easily bundle the required algorithm parameters into a named variant. In your example, minerd uses -a yespowerurx, which internally includes the specific parameters for UraniumX. But technically this is the same as explicitly passing yespower, n, r, key

Why does the only Bitok pool require custom mining settings?  (--param-n=2048 --param-r=32 --param-key="BitokPoW")

Is this to keep rented hash off the pool?

Not a pool quirk. Bitok uses a custom pow algorithm BitokPoW (modified YesPower).
https://github.com/elvisjedusor/bitok/blob/master/BITOKPOW.md

Not bulletproof against rented hash, but it raises the barrier for quick flash attacks. Smart move implementing it from start.

It looks like those extra coin specific settings could be implemented in the pools bitok.json
Bottom line Bitok needs more pools.

Miners must use those exact parameters or they will produce invalid hashes/shares.

More pools are needed. It's not hard to implement Bitok on an existing pool.

bitok is way more than standard, im liking what i see and i agree me you and three (:

[Tongpu]

cool 

https://bitokd.run/network

[neur0n.inc]

Yes, it's great. And the orange color is very suitable, bitok explorer looks nicer.

[Btc_order]

Do you guys know if any vps platform or something like that can mine with cpu?

[aviestegmeier]

Do you guys know if any vps platform or something like that can mine with cpu?

i don't really recommend you to mine on a rented vps/vds. Most of the cloud providers prohibit mining on rented devices.

[yoshikiazuma]

Do you guys know if any vps platform or something like that can mine with cpu?

i don't really recommend you to mine on a rented vps/vds. Most of the cloud providers prohibit mining on rented devices.

i agree. use it for personal gains on a personal computers.

[Btc_order]

Do you guys know if any vps platform or something like that can mine with cpu?

i don't really recommend you to mine on a rented vps/vds. Most of the cloud providers prohibit mining on rented devices.

i agree. use it for personal gains on a personal computers.

it was to have more power

[aviestegmeier]

Do you guys know if any vps platform or something like that can mine with cpu?

i don't really recommend you to mine on a rented vps/vds. Most of the cloud providers prohibit mining on rented devices.

i agree. use it for personal gains on a personal computers.

it was to have more power

Technically you could try.. but cloud provider will most likely terminate your server and account and you won't receive a refund for that. You could try to rent hash power from nicehash but i don't really sure if they support yespower algorithm. There is also providers available that rent cpu and gpu power for ai stuff, but with a few tweaks i guess you can use them for bitok mining too.

[Btc_order]

Do you guys know if any vps platform or something like that can mine with cpu?

i don't really recommend you to mine on a rented vps/vds. Most of the cloud providers prohibit mining on rented devices.

i agree. use it for personal gains on a personal computers.

it was to have more power

Technically you could try.. but cloud provider will most likely terminate your server and account and you won't receive a refund for that. You could try to rent hash power from nicehash but i don't really sure if they support yespower algorithm. There is also providers available that rent cpu and gpu power for ai stuff, but with a few tweaks i guess you can use them for bitok mining too.

can you send me the link of the ai for mining?

[elvisjedusor]

The privacy model in the Bitcoin whitepaper was always meant to be stronger than what the network delivered in practice. Satoshi knew this. He researched key blinding. He sketched out network-level unlinkability. He recommended Tor. He said addresses should be used only once.

Bitok takes these ideas and makes them real, in working code, in a way that is compatible with the original protocol design. No forks. No new trust assumptions. Just the privacy that was always supposed to be there.

This is the first feature, and it is the one Satoshi described most concretely. I have implemented it exactly as he envisioned: blinded variations of a public key, where each payment goes to a unique, unlinkable address, and only the intended recipient can detect and spend the funds.

Read more: https://github.com/elvisjedusor/bitok/blob/master/docs/PRIVACY.md

Commit: https://github.com/elvisjedusor/bitok/commit/b3f4d67246d58a673fc99b93c6ecc21a3cbcb5d6

Stealth ok-addresses support will be included in next Bitok release

How it works:

You have ONE stealth ok-address (for ex. okCQyc...N5NX). When someone sends you coins, the protocol automatically generates a brand new, unique one-time address for that specific transaction. So on the blockchain, every payment to you looks like it goes to a completely different address, no one can link them together or see they all belong to you.

The two secrets:

Scan secret - lets your wallet scan the blockchain and detect "this transaction is mine"
Spend secret - lets you actually spend those coins

Backup / Recovery:

You only need to save those two secrets (scan_secret + spend_secret). That's it. You can throw away the wallet.dat, set up a completely fresh wallet on a new machine, import those two secrets, and your wallet will:
Scan the blockchain
Find all transactions that were sent to your stealth address
Derive all the one-time private keys needed to spend them
Show your full balance

In a simple words two WIF keys on a piece of paper is your entire backup. No need to keep track of hundreds of generated addresses or back up wallet.dat after every transaction. That's the main advantage ok-addresses over regular addresses.

[yoshikiazuma]

The privacy model in the Bitcoin whitepaper was always meant to be stronger than what the network delivered in practice. Satoshi knew this. He researched key blinding. He sketched out network-level unlinkability. He recommended Tor. He said addresses should be used only once.

Bitok takes these ideas and makes them real, in working code, in a way that is compatible with the original protocol design. No forks. No new trust assumptions. Just the privacy that was always supposed to be there.

This is the first feature, and it is the one Satoshi described most concretely. I have implemented it exactly as he envisioned: blinded variations of a public key, where each payment goes to a unique, unlinkable address, and only the intended recipient can detect and spend the funds.

Read more: https://github.com/elvisjedusor/bitok/blob/master/docs/PRIVACY.md

Commit: https://github.com/elvisjedusor/bitok/commit/b3f4d67246d58a673fc99b93c6ecc21a3cbcb5d6

Stealth ok-addresses support will be included in next Bitok release

How it works:

You have ONE stealth ok-address (for ex. okCQyc...N5NX). When someone sends you coins, the protocol automatically generates a brand new, unique one-time address for that specific transaction. So on the blockchain, every payment to you looks like it goes to a completely different address, no one can link them together or see they all belong to you.

The two secrets:

Scan secret - lets your wallet scan the blockchain and detect "this transaction is mine"
Spend secret - lets you actually spend those coins

Backup / Recovery:

You only need to save those two secrets (scan_secret + spend_secret). That's it. You can throw away the wallet.dat, set up a completely fresh wallet on a new machine, import those two secrets, and your wallet will:
Scan the blockchain
Find all transactions that were sent to your stealth address
Derive all the one-time private keys needed to spend them
Show your full balance

In a simple words two WIF keys on a piece of paper is your entire backup. No need to keep track of hundreds of generated addresses or back up wallet.dat after every transaction. That's the main advantage ok-addresses over regular addresses.

 i first met my first cryptonote coin back in 2012-13, mined my first ever coins. now lost (but the dice later changed in 2014. and which i missed and later to find out what those two were about, i was late).

i like the idea of bitokoin to incorporate a sense of privacy too (:

because as you mention because bitcoin has the tools built in to achieve those goals

i also think that quantum resistance would be necessary before the future takes hold of bitokoin

and a some solution to having a stable coin mechanism between bitok (bitok's very own designed stable coin built in)

im looking forwards to the next software release