tonych (OP)
Legendary
Offline
Activity: 965
Merit: 1033
|
|
December 17, 2016, 08:38:12 AM |
|
Incidentally, I finished developing our trustless exchange bot a day ago, just when you started this discussion. How did you know? It will exchange only internal assets, not a replacement for poloniex etc.
Please provide some more details? how to use it? what internal assets you meant? Is it blackbyte? I don't see any other internal assets... I'll release it in a few days, need to make a few changes to the wallet too. This version of the exchange will work with public assets only, blackbytes are private.
|
Simplicity is beauty
|
|
|
tortellino
|
|
December 17, 2016, 09:04:25 AM |
|
@hermesesus: thanks, no i understand. so better use for linking a wallet adress that isn´t used for transfer (e.g. to exchanges). The problem is i use the ledger for safety aspects, so the only thing i can do is transfer again before 24th my savings in this address and don´t make any wihdrawals.
|
|
|
|
endlessskill
|
|
December 17, 2016, 10:14:37 AM |
|
Will buy some BTC before 24th.
WIll buy some BTC too ))
|
|
|
|
tonych (OP)
Legendary
Offline
Activity: 965
Merit: 1033
|
|
December 17, 2016, 01:59:19 PM |
|
Not sure if you guys are already aware about but the Dutch translation is terrible. Don't hope this guy devpol did get paid for his automatically translation work done by a service like google translate. Translation work should be done by a native Dutch speaker. It was unsolicited, and the topic is now removed.
|
Simplicity is beauty
|
|
|
BALIK
Copper Member
Hero Member
Offline
Activity: 2254
Merit: 608
🍓 BALIK Never DM First
|
|
December 17, 2016, 03:39:53 PM |
|
Will buy some BTC before 24th.
if you want get free byteball use linking bitcoin addres you must linked addres before chrismast don't late after christmast can not get byteball coin again Oh, Can you please PM or post here the page of tutorial how to linked the bitcoin address, I saw it last days but I forget what pages is it?
|
|
|
|
|
tobsnn
|
|
December 17, 2016, 05:35:36 PM |
|
.1 BTC Bounty for someone to write up a tutorial on linking Trezor or Ledger wallet to Byteball account via signing a message. This should include details on what needs to be done with full balance (do we need to send it to one address within wallet) before signing message. Thanks.
Here you go 1NXoWMpvHX7FamzXDB5e9LEqQHVFY3fE7G Tutorial on linking Trezor wallet to Byteball account via signing a messageStep 1: Get a NEW Trezor bitcoin address- Initialize your Trezor - You get a screen like this - Click on “your_account” tab (account page), then on "Transactions" tab - Select the "Receive" tab and click on the “More please +” button to get a NEW Trezor bitcoin address - Check that the receiving address is truly created by your TREZOR by clicking on the "eye" icon (“Show on TREZOR” feature): the receiving address displayed must be the same on your browser AND on your Trezor device. Step 2: Move your bitcoins to your NEW address- On your Trezor account page, click on "Send" tab - Enter your NEW receiving address (the one you got from step 1) in the "Destination address" field - Put the amount you want to send (you can send the maximum possible amount by pressing the "arrow" button) - Click on "Send" - Enter your PIN - Check the amount of the transaction and the destination address and confirm your transaction on your Trezor (right button) Step 3: Install and launch Byteball wallet- Download Byteball wallet from byteball.org (make sure it is the LIVENET version) - Install Byteball wallet - Open Byteball wallet - Click on the link provided by byteball.org to launch the Transition Bot - Click on "Insert my address" then on "Send" - Enter your Trezor bitcoin address (the one from Step 1) and click on "Send" Step 4: Sign a message (your Byteball address) with your Trezor Bitcoin address- On your Trezor account page, press Sign & Verify in the top right corner - Copy & paste your Byteball address into the "Message" field of "Sign message" - Copy & paste your Trezor bitcoin address into the "Address" field of "Sign message" - Click on "Sign" - Check the message on your Trezor display and confirm - The signature should now appear on the screen, copy it Step 5: Link your Byteball address with your Trezor bitcoin address- In Byteball wallet, paste the signature (from step 4) and click on "Send" - You should get a confirmation from the Transition Bot with your current balance on your Trezor bitcoin address Note: If you spend your bitcoins, you will have to repeat Step 2, so that your bitcoins are always on the linked Trezor bitcoin address worth the 78$, thanks man
|
|
|
|
strasboug
|
|
December 17, 2016, 06:35:13 PM |
|
Incidentally, I finished developing our trustless exchange bot a day ago, just when you started this discussion. How did you know? It will exchange only internal assets, not a replacement for poloniex etc.
Please provide some more details? how to use it? what internal assets you meant? Is it blackbyte? I don't see any other internal assets... I'll release it in a few days, need to make a few changes to the wallet too. This version of the exchange will work with public assets only, blackbytes are private. what are public assets? is it something i can create myself using smart contract? is byteball supporting smart contract? what is the language used? is it supporting now? If so, will do a try.
|
|
|
|
bandarfjb
|
|
December 17, 2016, 07:01:24 PM |
|
Your current linked Bitcoin address is <xxx>
Please make sure that <xxx> is indeed your address and move all your coins to this address. The amount of bytes you receive will be proportional to the total balance of this Bitcoin address on December 25.
Current balance of this address is 0 BTC.
Current transition rate is 0.2081652227613 BTC per Gigabyte
---
I will transfer some BTC to my linked BTC address. Am I need to do something to update or just transfer the BTC to that address and everything will be ok?
|
|
|
|
journeym@n
Newbie
Offline
Activity: 28
Merit: 0
|
|
December 17, 2016, 07:28:56 PM |
|
Your current linked Bitcoin address is <xxx>
Please make sure that <xxx> is indeed your address and move all your coins to this address. The amount of bytes you receive will be proportional to the total balance of this Bitcoin address on December 25.
Current balance of this address is 0 BTC.
Current transition rate is 0.2081652227613 BTC per Gigabyte
---
I will transfer some BTC to my linked BTC address. Am I need to do something to update or just transfer the BTC to that address and everything will be ok?
You dont need to do anything but link BTC address properly. To check if it's properly linked (showing right amount of BTC), use transition bot link and its report inside BB live client.
|
|
|
|
peschi
|
|
December 17, 2016, 08:03:36 PM |
|
.1 BTC Bounty for someone to write up a tutorial on linking Trezor or Ledger wallet to Byteball account via signing a message. This should include details on what needs to be done with full balance (do we need to send it to one address within wallet) before signing message. Thanks.
Here you go 1NXoWMpvHX7FamzXDB5e9LEqQHVFY3fE7G Tutorial on linking Trezor wallet to Byteball account via signing a messageStep 1: Get a NEW Trezor bitcoin address- Initialize your Trezor - You get a screen like this - Click on “your_account” tab (account page), then on "Transactions" tab - Select the "Receive" tab and click on the “More please +” button to get a NEW Trezor bitcoin address - Check that the receiving address is truly created by your TREZOR by clicking on the "eye" icon (“Show on TREZOR” feature): the receiving address displayed must be the same on your browser AND on your Trezor device. Step 2: Move your bitcoins to your NEW address- On your Trezor account page, click on "Send" tab - Enter your NEW receiving address (the one you got from step 1) in the "Destination address" field - Put the amount you want to send (you can send the maximum possible amount by pressing the "arrow" button) - Click on "Send" - Enter your PIN - Check the amount of the transaction and the destination address and confirm your transaction on your Trezor (right button) Step 3: Install and launch Byteball wallet- Download Byteball wallet from byteball.org (make sure it is the LIVENET version) - Install Byteball wallet - Open Byteball wallet - Click on the link provided by byteball.org to launch the Transition Bot - Click on "Insert my address" then on "Send" - Enter your Trezor bitcoin address (the one from Step 1) and click on "Send" Step 4: Sign a message (your Byteball address) with your Trezor Bitcoin address- On your Trezor account page, press Sign & Verify in the top right corner - Copy & paste your Byteball address into the "Message" field of "Sign message" - Copy & paste your Trezor bitcoin address into the "Address" field of "Sign message" - Click on "Sign" - Check the message on your Trezor display and confirm - The signature should now appear on the screen, copy it Step 5: Link your Byteball address with your Trezor bitcoin address- In Byteball wallet, paste the signature (from step 4) and click on "Send" - You should get a confirmation from the Transition Bot with your current balance on your Trezor bitcoin address Note: If you spend your bitcoins, you will have to repeat Step 2, so that your bitcoins are always on the linked Trezor bitcoin address worth the 78$, thanks man Great Tutorial! Absolutely worth 0.1 BTC. I think this kind of descriptions are very important to bring people to byteball. Thanks a lot!
|
|
|
|
sxafir
|
|
December 17, 2016, 08:05:05 PM |
|
|
|
|
|
piebeyb
Legendary
Offline
Activity: 2436
Merit: 1039
Bitcoin Trader
|
|
December 17, 2016, 08:11:41 PM |
|
I've been testing byteball wallet and it looks pretty good, at least I've sent bitcoin and just waiting for the distribution byteball in my wallet
|
Trade on the go. Anywhere, anytime.
|
|
|
freigeist
|
|
December 17, 2016, 08:12:28 PM |
|
Hello. Has anybody problems with the installation on linux 32 bit machine?! After running the "npm install" command within the byteball directory like described on github i have got lot of erros and warnings like: Hello.
Has anybody problems with the installation on linux 32 bit machine?!
After running the "npm install" command within the byteball directory like described on github i have got lot of erros and warnings like:
[code] npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm WARN prefer global coffee-script@1.10.0 should be installed with -g node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v48-linux-ia32.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.8 and node@6.9.2 (node-v48 ABI) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v48-linux-ia32.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.8 and node@6.9.2 (node-v48 ABI) (falling back to source compile with node-gyp) ../src/database.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE node_sqlite3::Database::New(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/database.cc:133:96: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("filename").ToLocalChecked(), info[0].As<String>(), ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../../nan/nan.h:47, from ../src/database.h:10, from ../src/database.cc:4: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/database.cc:134:86: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("mode").ToLocalChecked(), Nan::New(mode), ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../../nan/nan.h:47, from ../src/database.h:10, from ../src/database.cc:4: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginOpen(node_sqlite3::Database::Baton*)’: ../src/database.cc:144:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginClose(node_sqlite3::Database::Baton*)’: ../src/database.cc:230:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginExec(node_sqlite3::Database::Baton*)’: ../src/database.cc:525:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginLoadExtension(node_sqlite3::Database::Baton*)’: ../src/database.cc:625:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/statement.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE node_sqlite3::Statement::New(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/statement.cc:103:74: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("sql").ToLocalChecked(), sql, ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../src/statement.cc:2: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginPrepare(node_sqlite3::Database::Baton*)’: ../src/statement.cc:118:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ In file included from ../src/statement.cc:6:0: ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginBind(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:322:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Bind); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginGet(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:370:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Get); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginRun(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:438:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Run); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginAll(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:504:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(All); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginEach(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:601:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Each); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginReset(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:724:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Reset); ^
> secp256k1@3.2.2 install /home/******/byteball/node_modules/secp256k1 > npm run rebuild || echo "Secp256k1 bindings compilation fail. Pure JS implementation will be used."
> secp256k1@3.2.2 rebuild /home/******/byteball/node_modules/secp256k1 > node-gyp rebuild
make: Entering directory '/home/******/byteball/node_modules/secp256k1/build' CXX(target) Release/obj.target/secp256k1/src/addon.o CXX(target) Release/obj.target/secp256k1/src/privatekey.o CXX(target) Release/obj.target/secp256k1/src/publickey.o CXX(target) Release/obj.target/secp256k1/src/signature.o CXX(target) Release/obj.target/secp256k1/src/ecdsa.o CXX(target) Release/obj.target/secp256k1/src/ecdh.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/src/secp256k1.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/contrib/lax_der_parsing.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/contrib/lax_der_privatekey_parsing.o SOLINK_MODULE(target) Release/obj.target/secp256k1.node COPY Release/secp256k1.node make: Leaving directory '/home/******/byteball/node_modules/secp256k1/build'
> sqlite3@3.1.8 install /home/******/byteball/node_modules/sqlite3 > node-pre-gyp install --fallback-to-build
make: Entering directory '/home/******/byteball/node_modules/sqlite3/build' ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c TOUCH Release/obj.target/deps/action_before_build.stamp CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3150000/sqlite3.o AR(target) Release/obj.target/deps/sqlite3.a COPY Release/sqlite3.a CXX(target) Release/obj.target/node_sqlite3/src/database.o CXX(target) Release/obj.target/node_sqlite3/src/node_sqlite3.o CXX(target) Release/obj.target/node_sqlite3/src/statement.o SOLINK_MODULE(target) Release/obj.target/node_sqlite3.node COPY Release/node_sqlite3.node COPY /home/******/byteball/node_modules/sqlite3/lib/binding/node-v48-linux-ia32/node_sqlite3.node TOUCH Release/obj.target/action_after_build.stamp make: Leaving directory '/home/******/byteball/node_modules/sqlite3/build'
> phantomjs@1.9.20 install /home/******/byteball/node_modules/phantomjs > node install.js
PhantomJS not found on PATH Download already available at /tmp/phantomjs/phantomjs-1.9.8-linux-i686.tar.bz2 Verified checksum of previously downloaded file Extracting tar contents (via spawned process) Removing /home/******/byteball/node_modules/phantomjs/lib/phantom Copying extracted folder /tmp/phantomjs/phantomjs-1.9.8-linux-i686.tar.bz2-extract-1482004617658/phantomjs-1.9.8-linux-i686 -> /home/******/byteball/node_modules/phantomjs/lib/phantom Writing location.js file Done. Phantomjs binary available at /home/******/byteball/node_modules/phantomjs/lib/phantom/bin/phantomjs byteball-tn@0.7.1-t /home/******/byteball ├── adm-zip@0.4.7 ├── angular@1.6.0 ├── angular-mocks@1.6.0 ├── async@1.5.2 ├─┬ bhttp@1.2.4 ....
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: regedit@^2.2.6 (node_modules/regedit): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for regedit@2.2.6: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"ia32"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
Has anybody encuntered similar issues?! [/code]
|
|
|
|
o0o0
Legendary
Offline
Activity: 1596
Merit: 1021
|
|
December 17, 2016, 10:33:46 PM |
|
ok ive linked my addresses through signing. i take it if sig doesnt verify it gives an error? if so i guess im good to go for 25th.
just a few questions 1 - do we get equal blackbytes and normal byteballs in distribution? 2 - whats the base unit in byteball? e.g 1btc = 1.00000000 = 100,000,000 satoshi. im trying to find the base unit exchanges will use to give me an idea of how much byteball/value i have
|
|
|
|
tonych (OP)
Legendary
Offline
Activity: 965
Merit: 1033
|
|
December 17, 2016, 10:46:47 PM |
|
Hello. Has anybody problems with the installation on linux 32 bit machine?! After running the "npm install" command within the byteball directory like described on github i have got lot of erros and warnings like: Hello.
Has anybody problems with the installation on linux 32 bit machine?!
After running the "npm install" command within the byteball directory like described on github i have got lot of erros and warnings like:
[code] npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated node-uuid@1.4.7: use uuid module instead npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.4.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm WARN prefer global coffee-script@1.10.0 should be installed with -g node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v48-linux-ia32.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.8 and node@6.9.2 (node-v48 ABI) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(403): https://mapbox-node-binary.s3.amazonaws.com/sqlite3/v3.1.8/node-v48-linux-ia32.tar.gz node-pre-gyp ERR! Pre-built binaries not found for sqlite3@3.1.8 and node@6.9.2 (node-v48 ABI) (falling back to source compile with node-gyp) ../src/database.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE node_sqlite3::Database::New(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/database.cc:133:96: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("filename").ToLocalChecked(), info[0].As<String>(), ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../../nan/nan.h:47, from ../src/database.h:10, from ../src/database.cc:4: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/database.cc:134:86: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("mode").ToLocalChecked(), Nan::New(mode), ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../../nan/nan.h:47, from ../src/database.h:10, from ../src/database.cc:4: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginOpen(node_sqlite3::Database::Baton*)’: ../src/database.cc:144:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginClose(node_sqlite3::Database::Baton*)’: ../src/database.cc:230:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginExec(node_sqlite3::Database::Baton*)’: ../src/database.cc:525:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/database.cc: In static member function ‘static void node_sqlite3::Database::Work_BeginLoadExtension(node_sqlite3::Database::Baton*)’: ../src/database.cc:625:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ ../src/statement.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE node_sqlite3::Statement::New(Nan::NAN_METHOD_ARGS_TYPE)’: ../src/statement.cc:103:74: warning: ‘bool v8::Object::ForceSet(v8::Local<v8::Value>, v8::Local<v8::Value>, v8::PropertyAttribute)’ is deprecated: Use CreateDataProperty / DefineOwnProperty [-Wdeprecated-declarations] info.This()->ForceSet(Nan::New("sql").ToLocalChecked(), sql, ReadOnly); ^ In file included from /home/******/.node-gyp/6.9.2/include/node/v8.h:25:0, from /home/******/.node-gyp/6.9.2/include/node/node.h:42, from ../src/statement.cc:2: /home/******/.node-gyp/6.9.2/include/node/v8.h:2695:22: note: declared here bool ForceSet(Local<Value> key, Local<Value> value, ^ /home/******/.node-gyp/6.9.2/include/node/v8config.h:333:3: note: in definition of macro ‘V8_DEPRECATED’ declarator __attribute__((deprecated(message))) ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginPrepare(node_sqlite3::Database::Baton*)’: ../src/statement.cc:118:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), ^ In file included from ../src/statement.cc:6:0: ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginBind(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:322:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Bind); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginGet(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:370:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Get); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginRun(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:438:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Run); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginAll(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:504:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(All); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginEach(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:601:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Each); ^ ../src/statement.cc: In static member function ‘static void node_sqlite3::Statement::Work_BeginReset(node_sqlite3::Statement::Baton*)’: ../src/macros.h:125:9: warning: unused variable ‘status’ [-Wunused-variable] int status = uv_queue_work(uv_default_loop(), \ ^ ../src/statement.cc:724:5: note: in expansion of macro ‘STATEMENT_BEGIN’ STATEMENT_BEGIN(Reset); ^
> secp256k1@3.2.2 install /home/******/byteball/node_modules/secp256k1 > npm run rebuild || echo "Secp256k1 bindings compilation fail. Pure JS implementation will be used."
> secp256k1@3.2.2 rebuild /home/******/byteball/node_modules/secp256k1 > node-gyp rebuild
make: Entering directory '/home/******/byteball/node_modules/secp256k1/build' CXX(target) Release/obj.target/secp256k1/src/addon.o CXX(target) Release/obj.target/secp256k1/src/privatekey.o CXX(target) Release/obj.target/secp256k1/src/publickey.o CXX(target) Release/obj.target/secp256k1/src/signature.o CXX(target) Release/obj.target/secp256k1/src/ecdsa.o CXX(target) Release/obj.target/secp256k1/src/ecdh.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/src/secp256k1.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/contrib/lax_der_parsing.o CC(target) Release/obj.target/secp256k1/src/secp256k1-src/contrib/lax_der_privatekey_parsing.o SOLINK_MODULE(target) Release/obj.target/secp256k1.node COPY Release/secp256k1.node make: Leaving directory '/home/******/byteball/node_modules/secp256k1/build'
> sqlite3@3.1.8 install /home/******/byteball/node_modules/sqlite3 > node-pre-gyp install --fallback-to-build
make: Entering directory '/home/******/byteball/node_modules/sqlite3/build' ACTION deps_sqlite3_gyp_action_before_build_target_unpack_sqlite_dep Release/obj/gen/sqlite-autoconf-3150000/sqlite3.c TOUCH Release/obj.target/deps/action_before_build.stamp CC(target) Release/obj.target/sqlite3/gen/sqlite-autoconf-3150000/sqlite3.o AR(target) Release/obj.target/deps/sqlite3.a COPY Release/sqlite3.a CXX(target) Release/obj.target/node_sqlite3/src/database.o CXX(target) Release/obj.target/node_sqlite3/src/node_sqlite3.o CXX(target) Release/obj.target/node_sqlite3/src/statement.o SOLINK_MODULE(target) Release/obj.target/node_sqlite3.node COPY Release/node_sqlite3.node COPY /home/******/byteball/node_modules/sqlite3/lib/binding/node-v48-linux-ia32/node_sqlite3.node TOUCH Release/obj.target/action_after_build.stamp make: Leaving directory '/home/******/byteball/node_modules/sqlite3/build'
> phantomjs@1.9.20 install /home/******/byteball/node_modules/phantomjs > node install.js
PhantomJS not found on PATH Download already available at /tmp/phantomjs/phantomjs-1.9.8-linux-i686.tar.bz2 Verified checksum of previously downloaded file Extracting tar contents (via spawned process) Removing /home/******/byteball/node_modules/phantomjs/lib/phantom Copying extracted folder /tmp/phantomjs/phantomjs-1.9.8-linux-i686.tar.bz2-extract-1482004617658/phantomjs-1.9.8-linux-i686 -> /home/******/byteball/node_modules/phantomjs/lib/phantom Writing location.js file Done. Phantomjs binary available at /home/******/byteball/node_modules/phantomjs/lib/phantom/bin/phantomjs byteball-tn@0.7.1-t /home/******/byteball ├── adm-zip@0.4.7 ├── angular@1.6.0 ├── angular-mocks@1.6.0 ├── async@1.5.2 ├─┬ bhttp@1.2.4 ....
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: regedit@^2.2.6 (node_modules/regedit): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for regedit@2.2.6: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"ia32"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"ia32"})
Has anybody encuntered similar issues?! Looks like it completed successfully, despite warnings. Proceed to next steps.[/code]
|
Simplicity is beauty
|
|
|
tonych (OP)
Legendary
Offline
Activity: 965
Merit: 1033
|
|
December 17, 2016, 10:53:54 PM |
|
Incidentally, I finished developing our trustless exchange bot a day ago, just when you started this discussion. How did you know? It will exchange only internal assets, not a replacement for poloniex etc.
Please provide some more details? how to use it? what internal assets you meant? Is it blackbyte? I don't see any other internal assets... I'll release it in a few days, need to make a few changes to the wallet too. This version of the exchange will work with public assets only, blackbytes are private. what are public assets? is it something i can create myself using smart contract? is byteball supporting smart contract? what is the language used? is it supporting now? If so, will do a try. Public assets are assets whose transactions are recorded on the public database and visible to everyone, like in Bitcoin. Assets are created by sending a special message, this is a sample script https://github.com/byteball/headless-byteball/blob/master/play/create_asset.jsRead here about smart contracts https://bitcointalk.org/index.php?topic=1617816.0
|
Simplicity is beauty
|
|
|
Machina_US
|
|
December 18, 2016, 01:40:30 AM |
|
ok ive linked my addresses through signing. i take it if sig doesnt verify it gives an error? if so i guess im good to go for 25th.
just a few questions 1 - do we get equal blackbytes and normal byteballs in distribution? 2 - whats the base unit in byteball? e.g 1btc = 1.00000000 = 100,000,000 satoshi. im trying to find the base unit exchanges will use to give me an idea of how much byteball/value i have
i just want to ask a same question like that so if i linked my address with balance 1 btc how many byteball will i receive on 25 dec ?
|
|
|
|
pnuts2012
|
|
December 18, 2016, 03:12:50 AM |
|
Hello I downloaded both versions for android and want to link addresses problem is that it doesnt open the chatbot on forum page tried both testnet and livenet. Does this not work for androids please help.
|
|
|
|
o0o0
Legendary
Offline
Activity: 1596
Merit: 1021
|
|
December 18, 2016, 04:20:01 AM |
|
ok ive linked my addresses through signing. i take it if sig doesnt verify it gives an error? if so i guess im good to go for 25th.
just a few questions 1 - do we get equal blackbytes and normal byteballs in distribution? 2 - whats the base unit in byteball? e.g 1btc = 1.00000000 = 100,000,000 satoshi. im trying to find the base unit exchanges will use to give me an idea of how much byteball/value i have
i just want to ask a same question like that so if i linked my address with balance 1 btc how many byteball will i receive on 25 dec ? the value is changing as more link http://transition.byteball.org tells you the current value its roughly 4GB per 1btc. i want to know if GB or MB is the 1.00000000 unit in byteball. what unit will be the 1.0 value used on exchanges i.e 1byteball = 0.00000000 btc?
|
|
|
|
|