Running Bitok - 0.3.19 Mainnet

[Tongpu]

Bitok v0.3.20.0 Release. Major Upgrade

report to moderator, fake

[Tongpu]

..That requires a compelling narrative, one that positions this coin as an attempt to follow the path Satoshi originally envisioned for Bitcoin before it was diverted by powerful interests. There’s also a powerful emotional angle: giving people who regret missing Bitcoin in the early 2010s what feels like a second chance. That’s an incredibly strong story..
..strong branding, and a cohesive, compelling narrative that people can believe in..

I’m not a marketing guy, but I think narrative, emotional angle, branding, etc must coming from end products built on Bitok. From real usecases.

I’ve been following Bitok development since day one. And there’s something most people don’t see. To me, the development sequence is not random at all. I see Elvis following a very clear systems path: Reopen the execution surface - Make it safe - Make it usable - Externalize the power. That separation is extremely clean.

What I see is a conservative, bounded smart-contract layer built inside the original Bitcoin architecture, not bolted on top of it (like others do, so this really unique experiment). All previous Bitok releases were numbered 0.3.19.x. But the latest release has its own name Phoenix. I don’t think that’s a coincidence. I’m pretty sure we don’t even fully understand the real power of this release yet.

I’m currently studying Phoenix and the SDK. I’ve only researched part of it so far, and I already see potential to build real things on Bitok.
Here are just a few examples for one of new opcodes (or better to say old, coz designed by satoshi and removed by bitcoin core)

1. With Bitok’s deterministic covenants, you can create a UTXO that enforces:
“Every 30 days, X amount can go only to this address.”
No merchant custody. No monthly approvals. No repeated signatures. No token allowances.
Even Ethereum handles this clumsily. Useful for subscriptions .

2. Non-Custodial Crowdfunding with Automatic Refunds
A very understandable use case. You lock funds into a covenant:
If total collected ≥ target before a certain block height - creator receives funds.
Else - everyone automatically refunds.
No Kickstarter. No trust. No legal enforcement needed.

3. Trustless OTC / Atomic Payments
Example: “I will pay you only if this transaction pays X to Y.”
You enforce payment routing at the transaction-structure level. Funds cannot be redirected or modified. This is extremely powerful for:
Market makers, OTC desks, Structured deals, etc


The real narrative for Bitok in these terms can be: “Programmable money without a virtual machine.”

Or even simpler: Bitcoin is money. Bitok is programmable money.

Now Im going to research other opcodes and SDK

P.s. About logo.. we can keep original Satoshi’s design just fix BC to OK on coin image. Just suggestion

[aviestegmeier]

P.s. About logo.. we can keep original Satoshi’s design just fix BC to OK on coin image. Just suggestion

To be honest, I share a similar view. We can keep the original logo and customize it to make it unique to Bitok. I have a few logos I designed for Bitok in my spare time, but these were not inspired by the original logo. I drew them on my iPad while traveling on the subway, thinking they would look cool. Here are some of my trial pieces:

https://erenyener.de/bitok/new.png

https://erenyener.de/bitok/new-2.png

https://erenyener.de/bitok/new-3.png

https://erenyener.de/bitok/new-4.png

*feel free to roast me, im not a graphic designer (but drawing bluetooth logo on the subway is free)

3. Trustless OTC / Atomic Payments
Example: “I will pay you only if this transaction pays X to Y.”
You enforce payment routing at the transaction-structure level. Funds cannot be redirected or modified. This is extremely powerful for:
Market makers, OTC desks, Structured deals, etc

Escrow systems can be established on Bitok using this method.

Since the network hash rate is still quite low as it is a new venture, it is vulnerable to 51% attacks. Even if it cannot completely prevent a 51% attack, a native vault can be designed to protect bitok holders using op_cat. While this may not be complete protection, it could create a waiting period/timeframe to allow the bitok holder to recover their assets in the event of a breach and to prevent the attacker from escaping with the funds.

Code:

[Vault UTXO]
       |
       |  (Withdraw tx)
       v
[Timelocked UTXO]
       |
       |  (Delay time)
       v
[Free transfer to wallet]

OR

Code:

[Vault UTXO]
       |
       | (Recovery path - owner)
       v
[Safe address]

Under normal circumstances, anyone who possesses a wallet key can transfer the funds in the wallet to any address they wish. However, this is not the case under the Native Vault scheme. If the wallet key is stolen, even if the person with access to the wallet attempts to withdraw funds to their own address, the system can delay the transaction for a predetermined period (e.g., 288 blocks).

Code:

<current_block + 288>
OP_CHECKLOCKTIMEVERIFY
OP_DROP
<pubkey>
OP_CHECKSIG

Unlike Bitcoin, the active op_cat feature in Bitok allows each transaction to function like a small contract within itself via UTXO. Even if the keys are stolen, it can provide the wallet owner with sufficient time to take action and proceed to the recovery phase. Of course, the OP_CHECKLOCKTIMEVERIFY and OP_CHECKSEQUENCEVERIFY features are active in Bitcoin, but other functions are not as flexible as in Bitok. Bitok is much more programmable than the current Bitcoin.

[elvisjedusor]

Code:

[Vault UTXO]
       |
       |  (Withdraw tx)
       v
[Timelocked UTXO]
       |
       |  (Delay time)
       v
[Free transfer to wallet]

Under normal circumstances, anyone who possesses a wallet key can transfer the funds in the wallet to any address they wish. However, this is not the case under the Native Vault scheme. If the wallet key is stolen, even if the person with access to the wallet attempts to withdraw funds to their own address, the system can delay the transaction for a predetermined period (e.g., 288 blocks).

Code:

<current_block + 288>
OP_CHECKLOCKTIMEVERIFY
OP_DROP
<pubkey>
OP_CHECKSIG

The routing example is correct. If the transaction is constructed to commit to specific outputs, signatures enforce that structure. It cannot be modified without invalidating the spend.

On the vault point: Bitok does not implement OP_CHECKLOCKTIMEVERIFY or OP_CHECKSEQUENCEVERIFY. Before BIP65, Original Bitcoin used transaction-level locktime for HTLC-style constructions in prototypes and research. Im restored and modernized that model, you can find template in Bitok SDK:

https://github.com/elvisjedusor/bitok-sdk/blob/main/src/contract/hashlock.ts

Bitok Timelocks are enforced at the transaction level using nLockTime, not via script opcodes. Modern Bitcoin CLTV allows composability inside nested scripts. Bitok model keeps the script smaller and pushes timing logic to the tx layer.

Since the network hash rate is still quite low as it is a new venture, it is vulnerable to 51% attacks. Even if it cannot completely prevent a 51% attack, a native vault can be designed to protect bitok holders using op_cat. While this may not be complete protection, it could create a waiting period/timeframe to allow the bitok holder to recover their assets in the event of a breach and to prevent the attacker from escaping with the funds.

A 51% attack is about chain reorganization. Script cannot prevent that. Vault logic protects against key compromise, operational mistakes or unauthorized spending by someone with signing access. It does not protect against chain reorgs. Hashrate security is addressed at the consensus level, not through contracts.

Different layers.

[yoshikiazuma]

Bitok 0.3.19.10 “Phoenix” Released

Block 18,000 has been successfully crossed. Full Script execution is now active on mainnet.

New release completes the transaction construction, signing, and script development toolchain on top of the re-enabled 0.3.19 execution model.

Includes infrastructure for web3/dApp development.

All changes preserve the original transaction format and consensus structure.

Release: https://github.com/elvisjedusor/bitok/releases/tag/0.3.19.10

Downloads: https://bitokd.run/download

This release makes the re-enabled script system usable end-to-end: construction, signing, inspection, execution.

Upgrade recommended.

https://i.ibb.co/LhPxcctZ/image-21.jpg


Quick Bitok OFFICIAL links (always use only official links):

Block explorer bitokd.run
Bitok Github github.com/elvisjedusor/bitok
RPC API Docs RPC API
Free Bitok faucet freebitok.com
X (Twitter) x.com/bitok_coin
Downloads bitokd.run/download
WebWallet wallet.bitokd.run

Bitok SDK github.com/elvisjedusor/bitok-sdk

yes the phoenix resurrection has begun! (:

you know why iam the phoenix agent amd-ragon 87-(00) (: hehe get it (:

Thank you, I appreciate that  

I genuinely think this project is a great idea. Ironically, in a sea of altcoins all trying to do a hundred different things, it’s refreshing to see one that’s actually attempting to go back in time and explore a path that was never taken. I think that’s incredibly clever.

That said, my main concern is adoption. Just like Bitcoin, this token can only become meaningful if people use it, trade it, and talk about it. We could build the best chain in the world, but that won’t matter if no one engages with it. In that sense, branding could become a serious hurdle. There’s already another company called Bitok, and on top of that, Bitok appears to be a fairly common surname in Kenya. If you search for it on X, most of what you see is unrelated posts about individuals. That makes it much harder to stand out and gain traction.

For this project to succeed, we need people to feel genuinely excited about it. That requires a compelling narrative, one that positions this coin as an attempt to follow the path Satoshi originally envisioned for Bitcoin before it was diverted by powerful interests. There’s also a powerful emotional angle: giving people who regret missing Bitcoin in the early 2010s what feels like a second chance. That’s an incredibly strong story.

But to make that resonate, we’ll need a trustworthy team, strong branding, and a cohesive, compelling narrative that people can believe in.

For the record, I do believe that this could be a very successful project.

bit-ok = bito-k = bito-koin

"ok-ay" zipnoid (:

[zipnoid]

bit-ok = bito=k = bito-koin

"ok-ay" zipnoid (:

hahaha I like that!

[garmin]

..That requires a compelling narrative, one that positions this coin as an attempt to follow the path Satoshi originally envisioned for Bitcoin before it was diverted by powerful interests. There’s also a powerful emotional angle: giving people who regret missing Bitcoin in the early 2010s what feels like a second chance. That’s an incredibly strong story..
..strong branding, and a cohesive, compelling narrative that people can believe in..

I’m not a marketing guy, but I think narrative, emotional angle, branding, etc must coming from end products built on Bitok. From real usecases.

I’ve been following Bitok development since day one. And there’s something most people don’t see. To me, the development sequence is not random at all. I see Elvis following a very clear systems path: Reopen the execution surface - Make it safe - Make it usable - Externalize the power. That separation is extremely clean.

What I see is a conservative, bounded smart-contract layer built inside the original Bitcoin architecture, not bolted on top of it (like others do, so this really unique experiment). All previous Bitok releases were numbered 0.3.19.x. But the latest release has its own name Phoenix. I don’t think that’s a coincidence. I’m pretty sure we don’t even fully understand the real power of this release yet.

I’m currently studying Phoenix and the SDK. I’ve only researched part of it so far, and I already see potential to build real things on Bitok.
Here are just a few examples for one of new opcodes (or better to say old, coz designed by satoshi and removed by bitcoin core)

1. With Bitok’s deterministic covenants, you can create a UTXO that enforces:
“Every 30 days, X amount can go only to this address.”
No merchant custody. No monthly approvals. No repeated signatures. No token allowances.
Even Ethereum handles this clumsily. Useful for subscriptions .

2. Non-Custodial Crowdfunding with Automatic Refunds
A very understandable use case. You lock funds into a covenant:
If total collected ≥ target before a certain block height - creator receives funds.
Else - everyone automatically refunds.
No Kickstarter. No trust. No legal enforcement needed.

3. Trustless OTC / Atomic Payments
Example: “I will pay you only if this transaction pays X to Y.”
You enforce payment routing at the transaction-structure level. Funds cannot be redirected or modified. This is extremely powerful for:
Market makers, OTC desks, Structured deals, etc


The real narrative for Bitok in these terms can be: “Programmable money without a virtual machine.”

Or even simpler: Bitcoin is money. Bitok is programmable money.

Now Im going to research other opcodes and SDK

P.s. About logo.. we can keep original Satoshi’s design just fix BC to OK on coin image. Just suggestion

 

[Tongpu]

I like this variant, simple, cool

Btw

There’s already another company called Bitok, and on top of that, Bitok appears to be a fairly common surname in Kenya. If you search for it on X, most of what you see is unrelated posts about individuals. That makes it much harder to stand out and gain traction

I just checked X, there is almost no $BITOK content, so if we use this tag (with $), it will be easy to find posts about the Bitok blockchain

[yoshikiazuma]

https://i.postimg.cc/zBBMyZx3/imageedit-9-5171653366.png

I like this variant, simple, cool

Btw

There’s already another company called Bitok, and on top of that, Bitok appears to be a fairly common surname in Kenya. If you search for it on X, most of what you see is unrelated posts about individuals. That makes it much harder to stand out and gain traction

I just checked X, there is almost no $BITOK content, so if we use this tag (with $), it will be easy to find posts about the Bitok blockchain

i like both of them variants of the coin logo, looks cool either way (: both are original

yes we need contents and maybe also create the first mascot character or something for bitok-oin (:

[zipnoid]

I built a simple website explaining why Bitok matters to share with people I know.

Feel free to use it as well! The more people in the community, the better is for everyone!

https://www.whybitok.com

[yoshikiazuma]

I built a simple website explaining why Bitok matters to share with people I know.

Feel free to use it as well! The more people in the community, the better is for everyone!

https://www.whybitok.com

cool ill have a read, should be interesting (:

[Tongpu]

I built a simple website explaining why Bitok matters to share with people I know.

Great, but need some fixes i believe

Codebase
Modern (14+ years of changes)  | Satoshi's original v0.3.19 (Compatible with modern systems) PURE
Peer Discovery
DNS seeds | DNS seeds,  IRC bootstrap (optional) CLASSIC

Other info looks good. Maybe add section "Programmable money" coz working full script is our "killer feature" from latest release

[zipnoid]

Codebase
Modern (14+ years of changes)  | Satoshi's original v0.3.19 (Compatible with modern systems) PURE
Peer Discovery
DNS seeds | DNS seeds,  IRC bootstrap (optional) CLASSIC

Other info looks good. Maybe add section "Programmable money" coz working full script is our "killer feature" from latest release

Thank you, that's a great feedback.
I pushed the changes. For the programmable money piece I slapped something together quickly but will revisit it later today.

[Laheeboo]

Are we going to have a place where we gather like a discord or telegram or something? 

[neur0n.inc]

Hello. I have absolutely no idea how to overcome these errors (bitok-0.3.19.10) The same happens when compiling "native" and "x86-64-v3". But I need "x86-64". The same happened before, i.e. with earlier versions...

Code:

# pacman -S --needed mingw-w64-x86_64-gcc mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-db mingw-w64-x86_64-wxwidgets3.2 make
warning: mingw-w64-x86_64-gcc-15.2.0-11 is up to date -- skipping
warning: mingw-w64-x86_64-boost-1.90.0-3 is up to date -- skipping
warning: mingw-w64-x86_64-openssl-3.6.1-3 is up to date -- skipping
warning: mingw-w64-x86_64-db-6.2.32-1 is up to date -- skipping
warning: mingw-w64-x86_64-wxwidgets3.2-msw-3.2.9-1 is up to date -- skipping
warning: make-4.4.1-2 is up to date -- skipping
 there is nothing to do

# make -f makefile.mingw gui MARCH=x86-64
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/util.o util.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/script.o script.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/bitcoin_db.o bitcoin_db.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/net.o net.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/irc.o irc.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/main.o main.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/rpc.o rpc.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/init.o init.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/ui.o ui.cpp
In file included from headers.h:161,
                 from ui.cpp:5:
ui.cpp: In function 'bool ThreadSafeAskFee(int64, const std::string&, wxWindow*)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:206:9: note: in expansion of macro '_'
  206 |         _("This transaction requires a fee of %s.  "
      |         ^
In file included from headers.h:148:
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
ui.cpp: In member function 'virtual void CMainFrame::OnButtonNew(wxCommandEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:1374:40: note: in expansion of macro '_'
 1374 |                 wxMessageBox(strprintf(_("Rescan complete. Found %d transaction(s)."), nFound),
      |                                        ^
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
ui.cpp: In member function 'virtual void CSendingDialog::OnPaint(wxPaintEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2219:27: note: in expansion of macro '_'
 2219 |         strcpy(pszStatus, _("CANCELLED"));
      |                           ^
In file included from D:/Programs/msys2/mingw64/include/wx-3.2/wx/chartype.h:99,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/debug.h:17,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/defs.h:1040,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/wx.h:14,
                 from headers.h:39:
D:/Programs/msys2/mingw64/include/string.h:61:77: note: initializing argument 2 of 'char* strcpy(char*, const char*)'
   61 |   char * __cdecl strcpy(char * __restrict__ _Dest,const char * __restrict__ _Source);
      |                                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
ui.cpp: In member function 'bool CSendingDialog::Status()':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2250:27: note: in expansion of macro '_'
 2250 |         strcpy(pszStatus, _("CANCELLED"));
      |                           ^
D:/Programs/msys2/mingw64/include/string.h:61:77: note: initializing argument 2 of 'char* strcpy(char*, const char*)'
   61 |   char * __cdecl strcpy(char * __restrict__ _Dest,const char * __restrict__ _Source);
      |                                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
ui.cpp: In member function 'virtual void CAddressBookDialog::OnButtonNew(wxCommandEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2856:44: note: in expansion of macro '_'
 2856 |                     wxMessageBox(strprintf(_("Rescan complete. Found %d transaction(s)."), nFound),
      |                                            ^
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
make: *** [makefile.mingw:236: obj/gui/ui.o] Error 1

I have no problems compiling "bitokd". And it doesn't matter to me whether libs are included in the executable file or not. It's just that in my case, 4 files are required:
- libdb_cxx-6.2.dll
- libgcc_s_seh-1.dll
- libstdc++-6.dll
- libwinpthread-1.dll

[neur0n.inc]

https://i.postimg.cc/kGLkr1FZ/imageedit-8-2556393696.png

I prefer this option. But I think there are too many stars here. And instead of two "BITOK", I think it's better one "BIT" at the top in a larger font.

[aviestegmeier]

Hello. I have absolutely no idea how to overcome these errors (bitok-0.3.19.10) The same happens when compiling "native" and "x86-64-v3". But I need "x86-64". The same happened before, i.e. with earlier versions...

Code:

# pacman -S --needed mingw-w64-x86_64-gcc mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-db mingw-w64-x86_64-wxwidgets3.2 make
warning: mingw-w64-x86_64-gcc-15.2.0-11 is up to date -- skipping
warning: mingw-w64-x86_64-boost-1.90.0-3 is up to date -- skipping
warning: mingw-w64-x86_64-openssl-3.6.1-3 is up to date -- skipping
warning: mingw-w64-x86_64-db-6.2.32-1 is up to date -- skipping
warning: mingw-w64-x86_64-wxwidgets3.2-msw-3.2.9-1 is up to date -- skipping
warning: make-4.4.1-2 is up to date -- skipping
 there is nothing to do

# make -f makefile.mingw gui MARCH=x86-64
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/util.o util.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/script.o script.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/bitcoin_db.o bitcoin_db.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/net.o net.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/irc.o irc.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/main.o main.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/rpc.o rpc.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/init.o init.cpp
g++ -c -std=c++11 -O3 -march=x86-64 -fomit-frame-pointer -mthreads -w -Wno-invalid-offsetof -Wformat -D_WIN32_WINNT=0x0A00   -DWIN32 -D_WINDOWS -DNOPCH -DOPENSSL_SUPPRESS_DEPRECATED -DNOPCH -D_FILE_OFFSET_BITS=64 -DOPENSSL_SUPPRESS_DEPRECATED -DwxUSE_GUI=1 -DWIN32 -D__WXMSW__ -ID:/Programs/msys2/mingw64/lib/wx/include/msw-unicode-3.2 -ID:/Programs/msys2/mingw64/include/wx-3.2 -DWXUSINGDLL -D__WXMSW__ -I"." -I"/mingw64/include" -I"/mingw64/include/wx-3.2" -o obj/gui/ui.o ui.cpp
In file included from headers.h:161,
                 from ui.cpp:5:
ui.cpp: In function 'bool ThreadSafeAskFee(int64, const std::string&, wxWindow*)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:206:9: note: in expansion of macro '_'
  206 |         _("This transaction requires a fee of %s.  "
      |         ^
In file included from headers.h:148:
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
ui.cpp: In member function 'virtual void CMainFrame::OnButtonNew(wxCommandEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:1374:40: note: in expansion of macro '_'
 1374 |                 wxMessageBox(strprintf(_("Rescan complete. Found %d transaction(s)."), nFound),
      |                                        ^
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
ui.cpp: In member function 'virtual void CSendingDialog::OnPaint(wxPaintEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2219:27: note: in expansion of macro '_'
 2219 |         strcpy(pszStatus, _("CANCELLED"));
      |                           ^
In file included from D:/Programs/msys2/mingw64/include/wx-3.2/wx/chartype.h:99,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/debug.h:17,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/defs.h:1040,
                 from D:/Programs/msys2/mingw64/include/wx-3.2/wx/wx.h:14,
                 from headers.h:39:
D:/Programs/msys2/mingw64/include/string.h:61:77: note: initializing argument 2 of 'char* strcpy(char*, const char*)'
   61 |   char * __cdecl strcpy(char * __restrict__ _Dest,const char * __restrict__ _Source);
      |                                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
ui.cpp: In member function 'bool CSendingDialog::Status()':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2250:27: note: in expansion of macro '_'
 2250 |         strcpy(pszStatus, _("CANCELLED"));
      |                           ^
D:/Programs/msys2/mingw64/include/string.h:61:77: note: initializing argument 2 of 'char* strcpy(char*, const char*)'
   61 |   char * __cdecl strcpy(char * __restrict__ _Dest,const char * __restrict__ _Source);
      |                                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
ui.cpp: In member function 'virtual void CAddressBookDialog::OnButtonNew(wxCommandEvent&)':
uibase.h:15:14: error: cannot convert 'wxString' to 'const char*'
   15 | #define _(s) wxString(wxT(s))
      |              ^~~~~~~~~~~~~~~~
      |              |
      |              wxString
ui.cpp:2856:44: note: in expansion of macro '_'
 2856 |                     wxMessageBox(strprintf(_("Rescan complete. Found %d transaction(s)."), nFound),
      |                                            ^
util.h:131:30: note: initializing argument 1 of 'std::string strprintf(const char*, ...)'
  131 | string strprintf(const char* format, ...);
      |                  ~~~~~~~~~~~~^~~~~~
make: *** [makefile.mingw:236: obj/gui/ui.o] Error 1

I have no problems compiling "bitokd". And it doesn't matter to me whether libs are included in the executable file or not. It's just that in my case, 4 files are required:
- libdb_cxx-6.2.dll
- libgcc_s_seh-1.dll
- libstdc++-6.dll
- libwinpthread-1.dll

First of all close all the bitok services from task manager.

install essentials

Code:

sudo apt update

sudo apt install build-essential \
  libssl-dev \
  libdb4.8-dev \
  libdb4.8++-dev \
  libwxgtk2.8-dev \
  libboost-all-dev \
  git

if unable to find libwx try this

Code:

sudo add-apt-repository universe
sudo apt update

Go to bitok file on terminal

for daemon:

Code:

make -f makefile.unix

for GUI version:

Code:

make -f makefile.unix USE_UPNP=-

------

2nd method

instead of

Code:

strprintf(_("Rescan complete. Found %d transaction(s)."), nFound)

use

Code:

strprintf(_("Rescan complete. Found %d transaction(s).").mb_str(), nFound)

or

Code:

strprintf(_("Rescan complete. Found %d transaction(s).").ToStdString().c_str(), nFound)

Then

instead of

Code:

strcpy(pszStatus, _("CANCELLED"));

use

Code:

strcpy(pszStatus, _("CANCELLED").mb_str());

instead of

Code:

#define _(s) wxString(wxT(s))

use

Code:

#define _(s) wxString(wxT(s)).mb_str()

----
3rd method

İf those wont work install wxWidget 2.8 via wget

Code:

wget https://github.com/wxWidgets/wxWidgets/archive/refs/tags/v2.8.12.tar.gz
tar -xzf v2.8.12.tar.gz
cd wxWidgets-2.8.12

Code:

./configure \
  --host=x86_64-w64-mingw32 \
  --build=x86_64-w64-mingw32 \
  --disable-shared \
  --enable-static \
  --disable-unicode \
  --with-msw \
  --with-opengl \
  --without-subdirs

Code:

make -j4
make install

if you face with error try this and than retry installation

Code:

pacman -S mingw-w64-x86_64-toolchain \
         mingw-w64-x86_64-libpng \
         mingw-w64-x86_64-libjpeg-turbo \
         mingw-w64-x86_64-tiff \
         mingw-w64-x86_64-expat \
         mingw-w64-x86_64-zlib

And finally go to cd bitokd (or where bitok located)

Code:

make -f makefile.mingw gui MARCH=x86-64 \
    WXINCLUDEPATH=/mingw64/include/wx-2.8 \
    WXLIBPATH=/mingw64/lib

[elvisjedusor]

Hello. I have absolutely no idea how to overcome these errors (bitok-0.3.19.10) The same happens when compiling "native" and "x86-64-v3". But I need "x86-64". The same happened before, i.e. with earlier versions...

Patched for wxWidgets 3.2. The issue was that wxWidgets 3.2 with GCC 15 on MinGW no longer allows implicit conversion from wxString to const char*.

Please pull from git and try building again, following the instructions. The windows GUI wallet should build successfully now.

[Tongpu]

Working on a Developer Mode for the web wallet with a simple UI. It will allow anyone to program on Bitok, from pro developers to regular users. Bitok is programmable money, so every user should be able to easily program their own money.

Once it’s complete, I’ll open a pull request to the SDK/wallet repository. I hope Elvis will merge it after review. Wish me luck

I believe the future of crypto lies in a return to its cypherpunk roots. The market will soon realize that blockchain’s value goes far beyond memecoins, swing traders, layers, modern BIP's and other shit.
Bitok is our legacy, our second chance, we must preserve it and never change the consensus, only build on the foundations that Satoshi originally laid. Thanks Elvis for starting this cool thing. Im building here with great pleasure.