 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
Hi DEV! no news is not foreseen? can we disperse?
this was launched as an academic coin. Make something that uses this coin. Hi everyone, By the end of this month, I'm planning to create a command called "notarize" on simplewallet, which will be first released on b1tes TESTNET source code. The "notarize" command will be used to exclusively to timestamp hashed-data to transactions. Once it's successfully tested on b1tes TESTNET, it will be released on b1tes CORE source code. |
|
|
|
I don't understand the transfer command. How do I send B1TES to another address? help gives me: transfer transfer <mixin_count> <addr_1> <amount_1> [<addr_2> <amount_2> ... <addr_N> <amount_N>] [payment_id] - Transfer <amount_1>,... <amount_N> to <address_1>,... <address_N>, respectively. <mixin_count> is the number of transactions yours is indistinguishable from (from 0 to maximum available) I have no idea what these parameters mean. Hi Brunt, please, follow the item 3 (Notarize data in the B1tes TESTNET blockchain) in the B1tes TESTNET instructions above. In item 3, there are instructions on how to use notarize date using the transfer command. |
|
|
|
Hi Dev, I've tested following your instruction, it seem to work without problems. The only thing that I don't know if it is right is that I've sand from my wallet to my wallets with some amount in it (13/17 b1tes) and when I do the timestamp verification it shows no amount. It's how it as to be? https://www.dropbox.com/s/woh9cv1bpcmva6x/Ver_timestamp_b1tes.jpgHi Galapagos, thanks for your help in testing it! If you verify the timestamp from the wallet that executed the transfer of funds (through the notarizations command in simplewallet), the amount transferred will be shown as 0. But if you verify the timestamp from the wallet that received the transfer of funds, the amount transferred will be shown as 13/17 b1tes. The code that informs the amount transferred is provided only to the wallet that receives transfer of funds. |
|
|
|
Hi Dev, I've tested following your instruction, it seem to work without problems. The only thing that I don't know if it is right is that I've sand from my wallet to my wallets with some amount in it (13/17 b1tes) and when I do the timestamp verification it shows no amount. It's how it as to be? https://www.dropbox.com/s/woh9cv1bpcmva6x/Ver_timestamp_b1tes.jpgHi Galapagos, thanks for your help in testing it! If you verify the timestamp from the wallet that executed the transfer of funds (through the notarizations command in simplewallet), the amount transferred will be shown as 0. But if you verify the timestamp from the wallet that received the transfer of funds, the amount transferred will be shown as 13/17 b1tes. The code that informs the amount transferred is provided only to the wallet that receives transfer of funds. |
|
|
|
Hi everyone, I would like to ask you to volunteer in testing and analysing the code of a functionality that timestamps data in the Blockchain which has been added to the B1tes TESTNET source code. The B1tes project is based on the source code of a cryptonote cryptocurrency called Aeon, which features untraceable payments and unlinkable transactions. For more info about the project, go to: https://bitcointalk.org/index.php?topic=2092537.msg20905435#msg20905435 To test the functionality that timestamps data in the Blockchain you have to install the B1tes TESTNET blockchain on linux following the instructions below. Instructions on how to: 1. Install B1tes TESTNET blockchain 2. Create a B1tes TESTNET wallet and mine B1tes TESTNET 3. Notarize data in the B1tes TESTNET blockchain 3.1. Notarize document file in the B1tes TESTNET blockchain 3.2. Notarize text in the B1tes TESTNET blockchain 4. Verify timestamp of notarized data in the B1tes TESTNET blockchain 1. Install B1tes TESTNET blockchain: - open your command line terminal - Execute the following commands to get the dependencies needed in order to setup the environment to run the B1tes TESTNET blockchain: - sudo apt-get install build-essential - sudo apt-get install git - sudo apt-get install cmake - sudo apt-get install libboost-all-dev - Clone B1tes TESTNET source code: - create a directory called testnet-b1tes by running the command: - mkdir testnet-b1tes - enter the testnet-b1tes directory by running the command: - cd testnet-b1tes - clone B1tes TESTNET source code by running the command: - git clone https://github.com/b1tes/testnet-b1t - enter the testnet-b1t directory by running the command: - cd testnet-b1t - build b1tes source code by running the command: - make - wait until building b1tes TESTNET source code is 100% complete - enter the build directory by running the command: - cd build/release/src/ - download B1tes blockchain by running the command: - ./testnet-b1tesd - leave this terminal command line open (it may take a couple of hours until the B1tes TESTNET blockchain is downloaded and synchronized to the network). - and open a new terminal command line in order to create a B1tes TESTNET wallet and mine B1tes TESTNET. (You’ll only be able to synchronize a B1tes TESTNET wallet to the network and mine B1tes TESTNET if the B1tes TESTNET blockchain is downloaded and synchronized to the network on another terminal command line running the command testnet-b1tesd concurrently.) 2. Create a B1tes TESTNET wallet and mine B1tes TESTNET: - complete instructions 1 in order to create a B1tes TESTNET wallet - and open a new terminal command line in order to create a B1tes TESTNET walled and mine B1tes TESTNET - enter B1tes TESTNET build directory by running the command: - cd ~your_directory~/testnet-b1tes/testnet-b1t/build/release/src - create a B1tes TESTNET wallet by running the command: - ./simplewallet - follow the instructions in order to Generate a new wallet by giving a wallet file name and password - finally, inside simplewallet’s command line program, start mining B1tes TESTNET by running the following command: - start_mining 3. Notarize data in the B1tes TESTNET blockchain: 3.1. Notarize document file in the B1tes TESTNET blockchain: - open a new terminal command line and install OpenSSL by running the command: - sudo apt-get install openssl - generate a SHA-256 signature through openssl by running the command: - openssl sha -sha256 filename - for example: openssl sha -sha256 /home/user/Documents/contract.pdf - keep a copy of the resulting SHA-256 signature, which should be pasted along with the next command - in simplewallet’s command line program, transfer funds to a wallet by running the command: - transfer 1 <wallet_address> <amount> <copy_of_the_resulting_SHA-256_signature> 3.2. Notarize text in the B1tes TESTNET blockchain: - access http://www.xorbin.com/tools/sha256-hash-calculator - type the text to be notarized in the data field - click on "Calculate SHA256 hash" - keep a copy of the resulting SHA-256 signature, which should be pasted along with the next command - in simplewallet’s command line program, transfer funds to a wallet by running the command: - transfer 1 <wallet_address> <amount> <copy_of_the_resulting_SHA-256_signature> 4. Verify timestamp of notarized data in the B1tes TESTNET blockchain: - in simplewallet’s command line program, refresh the wallet by running the command: - refresh - and verify the timestamp of notarized data by running the command: - notarizations <copy_of_the_resulting_SHA-256_signature> - please notice that, if you verify the timestamp from the wallet that executed the transfer of funds (through the notarizations command in simplewallet), the amount transferred will be shown as 0. But if you verify the timestamp from the wallet that received funds, the the exact amount transferred will be shown, as the code that informs the amount transferred is provided only to the wallet that receives transfer of funds. |
|
|
|
Well I made it, this is part of my testnet log: [wallet btestt]: start_mining 1
Mining started in daemon
[wallet btestt]: balance
balance: 0.000000000000, unlocked balance: 0.000000000000
[wallet btestt]: refresh
Starting refresh...
Height 26424, transaction <61544408e13a60c2c56eeb7338538bcc0205e688b8104ace9260dff5d4f2b0ef>, received 0.004403878321
Height 26424, transaction <61544408e13a60c2c56eeb7338538bcc0205e688b8104ace9260dff5d4f2b0ef>, received 0.050000000000
Height 26424, transaction <61544408e13a60c2c56eeb7338538bcc0205e688b8104ace9260dff5d4f2b0ef>, received 0.100000000000
Height 26424, transaction <61544408e13a60c2c56eeb7338538bcc0205e688b8104ace9260dff5d4f2b0ef>, received 7.000000000000
Height 26424, transaction <61544408e13a60c2c56eeb7338538bcc0205e688b8104ace9260dff5d4f2b0ef>, received 10.000000000000
Height 26425, transaction <2948c1b138ff50956c753f13f0acf0db8d1afa991eb724576336d0b34692a193>, received 0.004387518607
Height 26425, transaction <2948c1b138ff50956c753f13f0acf0db8d1afa991eb724576336d0b34692a193>, received 0.050000000000
Height 26425, transaction <2948c1b138ff50956c753f13f0acf0db8d1afa991eb724576336d0b34692a193>, received 0.100000000000
Height 26425, transaction <2948c1b138ff50956c753f13f0acf0db8d1afa991eb724576336d0b34692a193>, received 7.000000000000
Height 26425, transaction <2948c1b138ff50956c753f13f0acf0db8d1afa991eb724576336d0b34692a193>, received 10.000000000000
Height 26426, transaction <0bfaf6f4bd395decb8d4fd98f56ad70ce0ccbb8d0dc47ed32faf2db0395c8108>, received 0.004371158908
Height 26426, transaction <0bfaf6f4bd395decb8d4fd98f56ad70ce0ccbb8d0dc47ed32faf2db0395c8108>, received 0.050000000000
Height 26426, transaction <0bfaf6f4bd395decb8d4fd98f56ad70ce0ccbb8d0dc47ed32faf2db0395c8108>, received 0.100000000000
Height 26426, transaction <0bfaf6f4bd395decb8d4fd98f56ad70ce0ccbb8d0dc47ed32faf2db0395c8108>, received 7.000000000000
Height 26426, transaction <0bfaf6f4bd395decb8d4fd98f56ad70ce0ccbb8d0dc47ed32faf2db0395c8108>, received 10.000000000000
Height 26428, transaction <4ed1cbf81132ddbcbfcefb7f494a3e0c9d5b2b2ebba07e9a6dcd73c803f2a1be>, received 0.004338439557
Height 26428, transaction <4ed1cbf81132ddbcbfcefb7f494a3e0c9d5b2b2ebba07e9a6dcd73c803f2a1be>, received 0.050000000000
Height 26428, transaction <4ed1cbf81132ddbcbfcefb7f494a3e0c9d5b2b2ebba07e9a6dcd73c803f2a1be>, received 0.100000000000
Height 26428, transaction <4ed1cbf81132ddbcbfcefb7f494a3e0c9d5b2b2ebba07e9a6dcd73c803f2a1be>, received 7.000000000000
Height 26428, transaction <4ed1cbf81132ddbcbfcefb7f494a3e0c9d5b2b2ebba07e9a6dcd73c803f2a1be>, received 10.000000000000
Refresh done, blocks received: 294
balance: 360.329430016857, unlocked balance: 291.711929021464
[wallet btestt]: stop_mining
Mining stopped in daemon
[wallet btestt]: transfer 1 btestthBFVnWCRJuG9q4tiEom9FkARBHjBGyXxmKDnoF1nRUonh3UTxUdt5SZcnEw58GeLfx4DBjoHZJfA67cc877eimay8X9ah2g 10 5abd40e5329d536efce33a7bbc00ed2f81f49b3d10508a3d51ce748aa7b1fd61
Money successfully sent, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>
[wallet btestt]: transfer 1 btestthBFVnWCRJuG9q4tiEom9FkARBHjBGyXxmKDnoF1nRUonh3UTxUdt5SZcnEw58GeLfx4DBjoHZJfA67cc877eimay8X9ah2g 10 807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d
Money successfully sent, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>
[wallet btestt]: refresh
Starting refresh...
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, received 0.040000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, received 0.200000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, spent 0.050000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, spent 0.050000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, spent 0.050000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, spent 0.100000000000
Height 26432, transaction <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd>, spent 10.000000000000
Refresh done, blocks received: 5
balance: 340.309430016857, unlocked balance: 266.961929021464
[wallet btestt]: notarizations 5abd40e5329d536efce33a7bbc00ed2f81f49b3d10508a3d51ce748aa7b1fd61
payment transaction height amount unlock time timestamp
<5abd40e5329d536efce33a7bbc00ed2f81f49b3d10508a3d51ce748aa7b1fd61> <b73e7ce4197aa63256e524e4cc091883da8b3a07e5cd30fb11311295cda276cd> 26432 0.000000000000 0 Sat Jan 13 12:02:49 2018
[wallet btestt]: notarizations 807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d
payment transaction height amount unlock time timestamp
No payments with id <807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d>
[wallet btestt]: refresh
Starting refresh...
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, received 0.090000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, received 0.400000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, received 4.000000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 0.100000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 0.100000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 0.100000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 0.100000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 0.100000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 7.000000000000
Height 26435, transaction <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a>, spent 7.000000000000
Refresh done, blocks received: 3
balance: 340.309430016857, unlocked balance: 266.961929021464
[wallet btestt]: notarizations 807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d
payment transaction height amount unlock time timestamp
<807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d> <c26d57d828de11ddaf979e4a1a9adf1f7cb80a9d497e9dcf0e5551fcec63aa7a> 26435 0.000000000000 0 Sat Jan 13 12:06:24 2018
[wallet btestt]: I wish was correct. Yes, it's correct. The SHA-256_signature 807a34b90d63a58bcdc6c3344e4b01edd982a72291ea64994e5f23fb491d219d was timestamped on Sat Jan 13 12:06:24 2018 and SHA-256_signature 5abd40e5329d536efce33a7bbc00ed2f81f49b3d10508a3d51ce748aa7b1fd61 was timestamped on Sat Jan 13 12:02:49 2018. |
|
|
|
I can not help a lot, but have an old pc (Medion Akoya 2gb) with Xubuntu.
Despite i am a total noob in linux with yours instructions i am now build the source code (20%) I wish that i could finish all the instructions well.
I like your initiative, always think that CryptoNight-Lite is a very underrated Algo.
Edit: Ok, I mined some blocks, but I have some problems:
In the 3 step when "- openssl sha -sha256 filename", which filename?, because I need one, no?
And I need other address to send the amount, or I make it with simplewallet?
Thanks.
Hi, Thank you for volunteering. The filename can be a location of any kind of file that you would like to notarize. For example: openssl sha -sha256 /home/user/Documents/contract.pdf As for the wallet address, a wallet can transfer funds to itself using its own address to tranfer funds. Or you can create another wallet on simplewallet to tranfer funds to that wallet address. |
|
|
|
Hi everyone, I would like to ask you to volunteer in testing and analysing the code of a functionality that timestamps data in the Blockchain which has been added to the B1tes TESTNET source code. The B1tes project is based on the source code of a cryptonote cryptocurrency called Aeon, which features untraceable payments and unlinkable transactions. For more info about the project, go to: https://bitcointalk.org/index.php?topic=2092537.msg20905435#msg20905435 To test the functionality that timestamps data in the Blockchain you have to install the B1tes TESTNET blockchain on linux following the instructions below. Instructions on how to: 1. Install B1tes TESTNET blockchain 2. Create a B1tes TESTNET wallet and mine B1tes TESTNET 3. Notarize data in the B1tes TESTNET blockchain 3.1. Notarize document file in the B1tes TESTNET blockchain 3.2. Notarize text in the B1tes TESTNET blockchain 4. Verify timestamp of notarized data in the B1tes TESTNET blockchain 1. Install B1tes TESTNET blockchain: - open your command line terminal - Execute the following commands to get the dependencies needed in order to setup the environment to run the B1tes TESTNET blockchain: - sudo apt-get install build-essential - sudo apt-get install git - sudo apt-get install cmake - sudo apt-get install libboost-all-dev - Clone B1tes TESTNET source code: - create a directory called testnet-b1tes by running the command: - mkdir testnet-b1tes - enter the testnet-b1tes directory by running the command: - cd testnet-b1tes - clone B1tes TESTNET source code by running the command: - git clone https://github.com/b1tes/testnet-b1t - enter the testnet-b1t directory by running the command: - cd testnet-b1t - build b1tes source code by running the command: - make - wait until building b1tes TESTNET source code is 100% complete - enter the build directory by running the command: - cd build/release/src/ - download B1tes blockchain by running the command: - ./testnet-b1tesd - leave this terminal command line open (it may take a couple of hours until the B1tes TESTNET blockchain is downloaded and synchronized to the network). - and open a new terminal command line in order to create a B1tes TESTNET wallet and mine B1tes TESTNET. (You’ll only be able to synchronize a B1tes TESTNET wallet to the network and mine B1tes TESTNET if the B1tes TESTNET blockchain is downloaded and synchronized to the network on another terminal command line running the command testnet-b1tesd concurrently.) 2. Create a B1tes TESTNET wallet and mine B1tes TESTNET: - complete instructions 1 in order to create a B1tes TESTNET wallet - and open a new terminal command line in order to create a B1tes TESTNET walled and mine B1tes TESTNET - enter B1tes TESTNET build directory by running the command: - cd ~your_directory~/testnet-b1tes/testnet-b1t/build/release/src - create a B1tes TESTNET wallet by running the command: - ./simplewallet - follow the instructions in order to Generate a new wallet by giving a wallet file name and password - finally, inside simplewallet’s command line program, start mining B1tes TESTNET by running the following command: - start_mining 3. Notarize data in the B1tes TESTNET blockchain: 3.1. Notarize document file in the B1tes TESTNET blockchain: - open a new terminal command line and install OpenSSL by running the command: - sudo apt-get install openssl - generate a SHA-256 signature through openssl by running the command: - openssl sha -sha256 filename - for example: openssl sha -sha256 /home/user/Documents/contract.pdf - keep a copy of the resulting SHA-256 signature, which should be pasted along with the next command - in simplewallet’s command line program, transfer funds to a wallet by running the command: - transfer 1 <wallet_address> <amount> <copy_of_the_resulting_SHA-256_signature> 3.2. Notarize text in the B1tes TESTNET blockchain: - access http://www.xorbin.com/tools/sha256-hash-calculator - type the text to be notarized in the data field - click on "Calculate SHA256 hash" - keep a copy of the resulting SHA-256 signature, which should be pasted along with the next command - in simplewallet’s command line program, transfer funds to a wallet by running the command: - transfer 1 <wallet_address> <amount> <copy_of_the_resulting_SHA-256_signature> 4. Verify timestamp of notarized data in the B1tes TESTNET blockchain: - in simplewallet’s command line program, refresh the wallet by running the command: - refresh - and verify the timestamp of notarized data by running the command: - notarizations <copy_of_the_resulting_SHA-256_signature> - please notice that, if you verify the timestamp from the wallet that executed the transfer of funds (through the notarizations command in simplewallet), the amount transferred will be shown as 0. But if you verify the timestamp from the wallet that received funds, the the exact amount transferred will be shown, as the code that informs the amount transferred is provided only to the wallet that receives transfer of funds. |
|
|
|
Hi everyone, A B1tes Testnet has been launched. B1tes Testnet network seed nodes: 18.221.94.119; 34.238.98.221 Port used by the daemon to establish connections with p2p network: 60705 Port used by the daemon to interact with simplewallet (RPC): 60804 B1tes Testnet source code is available at: https://github.com/b1tes/testnet-b1t |
|
|
|
Hi everyone, A wiki for the B1tes project has been created at: https://b1tes.miraheze.org/Please feel free add content to it relevant to the B1tes project. |
|
|
|
Hi everyone, I posted a cryptonote mining pool source code on GitHub at: https://github.com/b1tes/mining-pool. You can build the source code to provide a mining pool service, or you can use the mining pool privately. With this mining pool source code, you can mine cryptonote based coins, including B1tes. |
|
|
|
Hi everyone, If the b1tesd.exe and simplewallet.exe executables that were uploaded on Github will not work on your Windows PC, you will have to build B1tes source code on your Windows PC following the instructions below. One user pointed out that when executing b1tesd.exe the error below shows up: !!! WARNING: This user is a newbie. If you are expecting a message from a more veteran member, then this is an imposter !!!
i can't run b1tesd.exe and log file :
2017-Oct-03 09:49:39.640334 b1tes v0.9.12.0()
2017-Oct-03 09:49:39.643334 Module folder: C:\Users\Administrator\Desktop\b1tesd.exe
2017-Oct-03 09:49:39.648334 Initializing p2p server...
2017-Oct-03 09:49:39.652335 ERROR c:\users\windows\documents\visual studio 2017\b1tes\t1b\src\p2p\net_node.inl:113 Exception at [node_server::init_config], what=bad allocation
2017-Oct-03 09:49:39.661335 ERROR c:\users\windows\documents\visual studio 2017\b1tes\t1b\src\p2p\net_node.inl:278 Failed to init config.
2017-Oct-03 09:49:39.668336 ERROR C:\Users\windows\Documents\Visual Studio 2017\b1tes\t1b\src\daemon\daemon.cpp:175 Failed to initialize p2p server.
2017-Oct-03 09:49:39.677336 Mining has been stopped, 0 finished
If you are getting a similar error, please build B1tes source code on your Windows PC following the instructions below: These instructions were adapted from this link: https://bitcointalk.org/index.php?topic=641696.msg18754693#msg18754693Building B1tes on Windows (Guide v2017.04.26) - Download and install latest Git https://github.com/git-for-windows/git/releases/download/v2.12.2.windows.2/Git-2.12.2.2-64-bit.exe- To compile b1tesd.exe and simplewallet.exe you will need to install vs2015 Community RTM (iso available to download here https://xinyustudio.wordpress.com/2015/07/21/visual-studio-2015-iso-download-links-official-directoffline-links/) http://download.microsoft.com/download/0/B/C/0BC321A4-013F-479C-84E6-4A2F90B11269/vs2015.com_enu.iso take care to uncheck box "visual studio 2015 update 3" else update 3 will be downloaded automatically. Important note: after installation you should be asked to reboot the OS. Do NOT forget this step, asked or not ! In addition to this, after rebooting you'll need to start Visual Studio Community 2015 GUI, as other components will be set up.  FYI, all version numbers can be found here https://omwtm.blog/2014/12/03/visual-studio-2013-version-numbers-and-updates/ https://omwtm.blog/2014/12/03/visual-studio-2013-version-numbers-and-updates/ - Download and install CMake version 3.8, win 32 installer. If you have a previous version uninstall it first. https://cmake.org/files/v3.8/cmake-3.8.0-rc4-win32-x86.msi- Download and install Python x86-64 executable installer, which is needed by CMake. If you have version 3.4 or lower uninstall it first. https://www.python.org/ftp/python/3.6.1/python-3.6.1-amd64.exe Pay attention when installation asks if you want to add to system path and do so. - Download ad install the pre-compiled Boost libraries v 1_63_00 for MSVC-14.0 64bit version (take note of their install path): https://sourceforge.net/projects/boost/files/boost-binaries/1.63.0/boost_1_63_0-msvc-14.0-64.exe/download Note: to build a distributable B1tes package you'll need to build Boost libraries from source, which it is indeed included in the download. Yet please bear in mind that the aim of my guide is to enable common B1tes users in Windows environment to be readily up to date with the latest B1tes release. The following directory should be added to compiler include paths (following my own installation path): D:\local\boost_1_63_0 The following directory should be added to linker library paths: D:\local\boost_1_63_0\lib64-msvc-14.0 This will be done by means of cmake arguments, below. - Now let's start the B1tes compiling procedure (16GB RAM is the minimum I would recommend in order to proceed successfully): Open “MSBuild Command Prompt for VS2015” or “Git Shell” or “Git bash” depending what you downloaded previously and do:
mkdir b1tes
cd b1tes
download B1tes source code
cd <B1tes root> press enter
mkdir build press enter
cd build press enter
cmake -G "Visual Studio 14 2015 Win64" -DBOOST_ROOT=D:\local\boost_1_63_0 -DBOOST_LIBRARYDIR=D:\local\boost_1_63_0\lib64-msvc-14.0 .. press enter
(the two dots are needed)
If the cmake gives errors issue this command instead:
cmake -G "Visual Studio 14 2015 Win64" -DBOOST_ROOT=D:/local/boost_1_63_0 -DBOOST_LIBRARYDIR=D:/local/boost_1_63_0/lib64-msvc-14.0 .. press enter
(the two dots are needed)
MSBuild Project.sln /p:Configuration=release /m press enter
After some time you'll find your .exe files in the path_to_your_b1tes_repository\Build\Src\Release directory. Alternative building procedure, using VS Community 2015 GUI: It is assumed that the cmake step has been done successfully. Close GIT Shell if still open. Open VS Community 2015 GUI File->Open-> Solution->path to b1tes local repository/Project.sln VS 2015 will then make a check of all includes. This will take some time, until in the lower-left corner you'll see "Ready". Patience! Be sure that up above Release and x64 are selected Build-> Build Solution You'll see a message when the building process is ended. You'll find your .exe files in the path_to_your_b1tes_repository\Build\Src\Release directory. In any case, after the exe files have been bult and copied in the position of your likings, always remember to clean the content inside the .../build directory to leave it ready for the very next build. This will obviously require Git Shell or MSVC 2015 GUI to be closed. |
|
|
|
Hi everyone, I still don't have good news regarding building B1tes on Windows. One user also tried to build it with no success. Below is a quote of our conversation:
Hi. Yes! You are on the right chain!
Were you able to build the New B1tes source code on Windows?
No sorry, no VB, and no time today. but i found my VM box and ubuntu version, so i am good to have my old coins please. I will try windows version poss tomorrow. J Hi, Please, try to build the New B1tes source code on Windows tomorrow. And let me know if you were able to do it. I tried to build the Windows binary from B1tes source code, but was unable to do it. I followed instructions of a file called README that is located in the root of the B1tes source code. Instructions on how to install the dependencies mentioned on README file are avaiable in a document on this link: https://github.com/forknote/cryptonote-generator/blob/master/docs/windows-requirements-install.mdI followed the documents' instructions, and I was successful in executing cmake: cmake -G "Visual Studio 12 Win64" -DBOOST_ROOT="c:\folder\to\boost_1_57_0" -DBOOST_LIBRARYDIR="c:\folder\to\boost_1_57_0\lib64-msvc-12.0" I wasn't successful when executing msbuild. By running this command "msbuild Project.sln /p:Configuration=Release", this error shows up: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets (57,5): error MSB8020: The build tools for v120 (Platform Toolset = 'v120') cannot be found. To build using the v120 bu ild tools, please install v120 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selec ting the Project menu or right-click the solution, and then selecting "Retarget solution". [C:\Users\LENOVO\Documents\V isual Studio 2017\b1tes\b1t\ZERO_CHECK.vcxproj] That is where I couldn't go any further on building B1tes on Windows. I hope you will be able to help. Hi, Similar issue...you need to find the exact version of VS Studio (12 x64). I cannot find it online anywhere, but without exact version you will not be able to compile. I don't believe you can get it from MS anymore, so you will have to ask around. I will let you know if i come across it, but most unlikely. Or, you could try say version 13, and copy/replace all refs in code....very trickly and likely to fail. prob best option is to ask on bitcointalk forum if anyone would give you a copy of VS12 J |
|
|
|
Hi everyone, There is a file called README that gives instructions on how to build B1tes on Windows. it's located on the root of B1tes source code. But before you follow README's instructions, you must first follow instructions on how to install all dependencies to build B1tes on Windows, which is available at: https://github.com/forknote/cryptonote-generator/blob/master/docs/windows-requirements-install.mdI followed the documents' instructions, and I was successful in executing cmake: cmake -G "Visual Studio 12 Win64" -DBOOST_ROOT="c:\folder\to\boost_1_57_0" -DBOOST_LIBRARYDIR="c:\folder\to\boost_1_57_0\lib64-msvc-12.0" When executing msbuild, I wasn't successful. By running this command "msbuild Project.sln /p:Configuration=Release", this error shows up: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.Cpp.Platform.targets (57,5): error MSB8020: The build tools for v120 (Platform Toolset = 'v120') cannot be found. To build using the v120 bu ild tools, please install v120 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selec ting the Project menu or right-click the solution, and then selecting "Retarget solution". [C:\Users\LENOVO\Documents\V isual Studio 2017\b1tes\b1t\ZERO_CHECK.vcxproj] That is where I couldn't go any further on building B1tes on Windows. I hope someone will be able to help. |
|
|
|
Old wallet worked?Where is new Windows qt wallet or only simple wallet?
Hi, the old B1tes wallet doesn's work with the new B1tes source code. There is no Windows QT wallet. Today I'm working on building a B1tes source code executable for Windows. |
|
|
|
I'm confused.
Is this open to new users yet or not?
Is the source code on the OP new or old?
It's open only to users who mined Old B1tes from Sep. 18 to Dec. 18. |
|
|
|
Hi everyone, The other B1tes announcement post is locked ( https://bitcointalk.org/index.php?topic=2092537.0). I keep getting the following message everytime I try post any message there: An Error Has Occurred! This topic is locked, you are not allowed to post or modify messages... So let's use this post to communicate with each other. |
|
|
|
|
