I have installed the nw.js package trough npm globally and run the within the byteball folder. The window opened but the content is a white page no buttons no any content. Do I need to wait for some time for something to appear or this could be some kind of error. Can you point me where should I look in case of error. which files should I check? It must be some kind of error. Right click, then both Inspect page and Inspect background page. Look for errors in the console. |
|
|
|
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 |
|
|
|
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] |
|
|
|
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. |
|
|
|
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. |
|
|
|
Besides, byteball will have built in decentralized exchange where most of trade will happen.
First time hearing this, can you elaborate? tonych mentioned it earlier in this thread, just do your search. No, he did not. Indeed he didn't. For the recored, the discussion concerning setting up a decentralized exchange can be found starting from https://bitcointalk.org/index.php?topic=1608859.msg16492233#msg16492233 and in the following less than 10 posts. Ok, he was talking about exchange which can be built on top of black bites. So next time please do your search and provide us with a proof link, thank you. Son, you better go give your advises to your mommy. Daddy here don't need them. Ok? It doesn't really help the community when you post bullshit, little man. Especially when it comes to concerns about exchange denominations and Byteball's ability to be listed. Citing some fictional built-in exchange as an actual solution shows that you really don't know shit. So please stop acting like you do. Ok, "built in" is not accurate phrase, I am not trying to deny this if you noticed. I did not cite nothing here, don't assign your fantasy to me. You asked me to elaborate about byteball exchange, I answered that there was a discussion earlier, which in fact took place. If you need details, you make your search, I am not going to do this. The discussion was about built on top exchange, not built in, which sounds interesting anyway, because when this will be implemented there will be no need to beg poloniex or other exchanges to include giga/mega etc bytes. This is even better approach than built in exchange, because independent group of devs can code it without messing with byteball core. 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. |
|
|
|
Quick Question; can we link multiple BTC addresses to our one Byteball address by sending the micro transaction from each BTC address, and do we have to run the Transition Bot each time?
You can (if you can control which address the payment is sent from, this is an advanced feature). You just send the same micro-amount to the same address. |
|
|
|
Tonych -
I set up my wallet. I sent my transaction from my blockchain.info wallet per the transition bots request. The incoming wallet address is 1LwrNbfBNQBchpycFBVu7q3xVXHsa3phpB.
I was told on this forum that the next step would be for me to send all my blockchain.info bitcoin to 1LwrNbfBNQBchpycFBVu7q3xVXHsa3phpB.
However, it doesn't look like I am in control of 1LwrNbfBNQBchpycFBVu7q3xVXHsa3phpB. Its had other transactions coming in and out of it that weren't mine in the past.
So, apparently the way I was told I could do all this while keeping my funds in my blockchain.info wallet doesn't work.
Please advise on what I should do? Thanks.
To have a list of your (used) addresses in blockchain.info, go to "Settings" --> "Addresses" , click on "Manage" then "Show" (Used Addresses) and click on "OK". Check if "1LwrNbfBNQBchpycFBVu7q3xVXHsa3phpB" is in the list Thank you for the instructions. The address 1LwrNbfBNQBchpycFBVu7q3xVXHsa3phpB is not on the list. I have 20 other addresses on the list. So what do I do now? You don't send anything to this address. You do a micropayment again (note the change in your total wallet balance), the bot will report another address, check this new address. |
|
|
|
is there any way planned to increase marketing apart from the sig campaign ?
I think this project will only succeed if we have a lot of users.
Any suggestions are welcome. We have sig campaign, twitter campaign, and a recent press release which resulted in a few publications. |
|
|
|
Filtering of microtransactions sent from exchange wallets already works in fully automated mode, so no need to apply any other measures.
Okay, well I might have missed something then. The last thing I remember, is you asking for someone to confirm that one suspect address was a Bittrex one (which it was), so I was under the impression that you filtered out exchanges' addresses manually once they were added, suspected and confirmed. It was the last manual intervention. Since then the algo has got better https://bitcointalk.org/index.php?topic=1608859.msg17132797#msg17132797. Okay, I assume you are talking about this: Now repeated attempts to link the same Bitcoin address will automatically blacklist this address.
I did see that, the keyword here for me is repeated, I understood that only a repeated attempt would be blacklisted, but if there's only one attempt to link an exchange address, what happens? Most will be immediately rejected because there will be more than two outputs. And there is always more than one cheater. |
|
|
|
Filtering of microtransactions sent from exchange wallets already works in fully automated mode, so no need to apply any other measures.
Okay, well I might have missed something then. The last thing I remember, is you asking for someone to confirm that one suspect address was a Bittrex one (which it was), so I was under the impression that you filtered out exchanges' addresses manually once they were added, suspected and confirmed. It was the last manual intervention. Since then the algo has got better https://bitcointalk.org/index.php?topic=1608859.msg17132797#msg17132797. |
|
|
|
The transition bot isn't working for me. I click on the link and nothing happens. Please advise. Thx.
Which os and which browser are you using? Be sure to have downloaded the correct livenet wallet (it's the second row of download links on the website). Is the wallet popping up when you click the link? I downloaded the Mac lite wallet. I am using Chrome and I also tried Firefox and opened the website on both. The wallet is not popping up. Does the wallet say [NEW TESTNET] at the top? |
|
|
|
It'll do as a very rough approximation, see the white paper for the exact criteria of finality.
Witnesses are expected to always emit transactions, that's one of the factors that determines the choice of witnesses.
But do witnesses have to do active transactions? That seem pretty random. It would be easier that witnesses will just do random transactions automatically (say transfer same amount to each other) so people's tx will be guaranteed to be confirmed after certain time? They don't need to transfer nothing. They need submit a smallest possible storage unit (cheapest) which does not change inputs or outputs, but only confirms previous transactions. They could do it, but my question is more on that is it automatic? Because if it does, then the confirmation time of any transactions can be guaranteed. Otherwise it all depends on the witness activities. This is interesting question. Suppose, each of 12 witnesses run a script which submit transactions at crazy rate, but nobody else is using the network at this time. What happens then? Do witnesses end up loosing money? Witnesses do post transactions automatically but do it in a bit more reasonable way https://github.com/byteball/byteball-witness/blob/master/start.jsOK will read the code. But what are the transactions they post automatically? do they send coins among themselves? Each witness just pays to itself. |
|
|
|
It'll do as a very rough approximation, see the white paper for the exact criteria of finality.
Witnesses are expected to always emit transactions, that's one of the factors that determines the choice of witnesses.
But do witnesses have to do active transactions? That seem pretty random. It would be easier that witnesses will just do random transactions automatically (say transfer same amount to each other) so people's tx will be guaranteed to be confirmed after certain time? They don't need to transfer nothing. They need submit a smallest possible storage unit (cheapest) which does not change inputs or outputs, but only confirms previous transactions. They could do it, but my question is more on that is it automatic? Because if it does, then the confirmation time of any transactions can be guaranteed. Otherwise it all depends on the witness activities. This is interesting question. Suppose, each of 12 witnesses run a script which submit transactions at crazy rate, but nobody else is using the network at this time. What happens then? Do witnesses end up loosing money? Witnesses do post transactions automatically but do it in a bit more reasonable way https://github.com/byteball/byteball-witness/blob/master/start.js |
|
|
|
The distribution model has become such a distraction it dominates the community conversation, should be speaking more about the merits of the technology and platform.
Yes all people are greedy and wish to get more, in a more "fair" deal to himself. Talking about tech stuff, I have a question: since there's no fixed block time, the tx happens as it comes, isn't that should be instant confirmation if there are enough activity going on? What is the delay of the confirmation? it heavily depend on the network activity? It is not instant, it takes a few minutes and depends on the overall activity in the network: the more activity, the faster. Why it is not instant? say if there are 1000 tx per second in the network, my transaction once done will be covered within a second by 50 other transactions, isn't that after 1 second my transaction will have 50 confirmations? If we put 10 confirmations as confirmed, isn't my tx is confirmed after less than 1 sec? Perhaps you got used to hear about N confirmations in Bitcoin. There is no such thing here, your transaction is either final or not. And getting covered advances it to being final. Getting covered by witnesses matters most (the structure of the DAG after your transaction also matters for finality). Witnesses earn fees from transactions they cover, and the more transactions per second there are in the network, the more frequently witnesses will post with positive ROI (they pay fees like everybody else). You will never get sub-second confirmation times because of network latency. OK so if I got it correctly, then if the transaction are covered by more than half witnesses' transactions it will be final thus confirmed? Are witnesses always emit transactions? What if none of the witness are doing tx? my tx will never get confirmed? It'll do as a very rough approximation, see the white paper for the exact criteria of finality. Witnesses are expected to always emit transactions, that's one of the factors that determines the choice of witnesses. |
|
|
|
The distribution model has become such a distraction it dominates the community conversation, should be speaking more about the merits of the technology and platform.
Yes all people are greedy and wish to get more, in a more "fair" deal to himself. Talking about tech stuff, I have a question: since there's no fixed block time, the tx happens as it comes, isn't that should be instant confirmation if there are enough activity going on? What is the delay of the confirmation? it heavily depend on the network activity? It is not instant, it takes a few minutes and depends on the overall activity in the network: the more activity, the faster. Why it is not instant? say if there are 1000 tx per second in the network, my transaction once done will be covered within a second by 50 other transactions, isn't that after 1 second my transaction will have 50 confirmations? If we put 10 confirmations as confirmed, isn't my tx is confirmed after less than 1 sec? Perhaps you got used to hear about N confirmations in Bitcoin. There is no such thing here, your transaction is either final or not. And getting covered advances it to being final. Getting covered by witnesses matters most (the structure of the DAG after your transaction also matters for finality). Witnesses earn fees from transactions they cover, and the more transactions per second there are in the network, the more frequently witnesses will post with positive ROI (they pay fees like everybody else). You will never get sub-second confirmation times because of network latency. |
|
|
|
The distribution model has become such a distraction it dominates the community conversation, should be speaking more about the merits of the technology and platform.
Yes all people are greedy and wish to get more, in a more "fair" deal to himself. Talking about tech stuff, I have a question: since there's no fixed block time, the tx happens as it comes, isn't that should be instant confirmation if there are enough activity going on? What is the delay of the confirmation? it heavily depend on the network activity? It is not instant, it takes a few minutes and depends on the overall activity in the network: the more activity, the faster. Tonych, is the model sort of proof of service? Those that relay the activity and transactions get rewarded some bytes? I read the whitepaper but still am looking for some sort of understanding of this. It is not a proof-of. The collected fees are split between regular users who are first to extend the DAG and witnesses who help define the order of transactions. |
|
|
|
The distribution model has become such a distraction it dominates the community conversation, should be speaking more about the merits of the technology and platform.
Yes all people are greedy and wish to get more, in a more "fair" deal to himself. Talking about tech stuff, I have a question: since there's no fixed block time, the tx happens as it comes, isn't that should be instant confirmation if there are enough activity going on? What is the delay of the confirmation? it heavily depend on the network activity? It is not instant, it takes a few minutes and depends on the overall activity in the network: the more activity, the faster. |
|
|
|
Hi tonych,
After this 25th snapshot, byteball and blackbytes will be distributed as per the rules you announced.
Byteball will be send to linked byteball addresses that reside on "byteball public DAG", I can understand this is completely asynchronous process..
What I cannot understand is about blackbytes distribution:
1) Is it an automatic or interactive process (need human intervention)?
2) Will byteball client with the linked keys on peoples computers need to be left running to receive these coins?
Thanks again.
1) It is automatic. 2) Not necessary, you'll see both bytes and blackbytes as soon as you start the wallet after the coins are sent out. |
|
|
|
|
Show Posts
