Obyte: Totally new consensus algorithm + private untraceable payments - page 908.

vlom

legendary

Activity: 1498

Merit: 1117

Quote from: SatoNatomato on February 05, 2017, 04:13:14 PM

Quote from: vlom on February 05, 2017, 03:38:28 PM

Quote from: tonych on February 03, 2017, 06:50:51 PM

Quote from: vlom on February 03, 2017, 01:28:36 PM

why does the OS X app try to connect to google?

plus.google.com TCP-Port 443 (https)

What makes you think so?
There are no references to any sites (except the default hub) in the source code.

because little snitch tells my that the app wants to connect.

Seems to be nwjs, the component used by Byteball. Maybe it means NodeWebKit.js and is the browser-bundled up.

Google is known for adding a bunch of shit in every source-code they touch to "resolve" something on their servers. This could be information leakage, especially when using it over Tor - who knows what it sends to Google even if it is the hostname and datetime its too much.

@tonych, maybe see if there is a default option which has to be turned off when importing/using nwjs?

edit: https://github.com/nwjs/nw.js/issues/5343 just one issue, expect 100 more "accidents" by google. edit2: if using the chromiu-args proxy workaround, make it something else than 127.0.0.1, like 127.6.6.6 to avoid more other problems.

everyone how is happy that i posted this can send my some bytes. i still don't have any.

ZLQAYBCCZT2DBBD6KSLXJYCYR6QMU2VK

thank you very much.

i am not sure if this is a security problem if you use a VPN.
but with tor? if not every connections is torified then this could really leak your IP.

i don't want to fud. i am just concerned about privacy. and i am not a hardcore techie.

escapefrom3dom

sr. member

Activity: 1932

Merit: 288

Quote from: johhnyUA on February 06, 2017, 05:29:45 AM

Quote from: Meuh5598i on February 06, 2017, 05:19:44 AM

Quote from: tonych on February 06, 2017, 03:58:45 AM

Quote from: BTCspace on February 05, 2017, 07:06:04 PM

Hi
tonych

maybe you can ask poloniex list byteball, so we can spread byteball to more people, as an developer you request counter more weight than community members.

thank you

here is the link:

https://poloniex.com/coinRequest

Requested a couple of times, no response so far. Maybe they wait for more votes?

Now a days they're not adding any good coin,unless you pay their fees for instant listing.A lots of new coins were added in poloniex,but not all of them are legit and good.

Poloniex it's very close to repeat the fate of Crypty (i mean exchanger) and MtGox. Very, very close.
Day after day this exchanger became more and more trustless. For me it's not good to spend our time to trying to add byteball to this excahnger.

why is that?

johhnyUA

legendary

Activity: 2436

Merit: 1849

Crypto for the Crypto Throne!

Quote from: Meuh5598i on February 06, 2017, 05:19:44 AM

Quote from: tonych on February 06, 2017, 03:58:45 AM

Quote from: BTCspace on February 05, 2017, 07:06:04 PM

Hi
tonych

maybe you can ask poloniex list byteball, so we can spread byteball to more people, as an developer you request counter more weight than community members.

thank you

here is the link:

https://poloniex.com/coinRequest

Requested a couple of times, no response so far. Maybe they wait for more votes?

Now a days they're not adding any good coin,unless you pay their fees for instant listing.A lots of new coins were added in poloniex,but not all of them are legit and good.

Poloniex it's very close to repeat the fate of Crypty (i mean exchanger) and MtGox. Very, very close.
Day after day this exchanger became more and more trustless. For me it's not good to spend our time to trying to add byteball to this excahnger.

Meuh5598i

full member

Activity: 253

Merit: 110

#epigencare #ICO https://ico.epigencare.com/

Quote from: tonych on February 06, 2017, 03:58:45 AM

Quote from: BTCspace on February 05, 2017, 07:06:04 PM

Hi
tonych

maybe you can ask poloniex list byteball, so we can spread byteball to more people, as an developer you request counter more weight than community members.

thank you

here is the link:

https://poloniex.com/coinRequest

Requested a couple of times, no response so far. Maybe they wait for more votes?

Now a days they're not adding any good coin,unless you pay their fees for instant listing.A lots of new coins were added in poloniex,but not all of them are legit and good.

escapefrom3dom

sr. member

Activity: 1932

Merit: 288

Quote from: lizidev on February 06, 2017, 04:24:25 AM

Quote from: tonych on February 06, 2017, 04:03:01 AM

Quote from: francisthecrusher on February 05, 2017, 10:15:24 PM

I read those sections, but (the way I understand it at least) at some point the network still relies on trusted nodes to function, leaving it wide open to sybil attacks.

Could you be more specific please, how would you sybil attack?

Dev:

Code:

Could not sent payment:know bad

Why send is so unstable,It have a lot of bugs.

specife the sendind issue.

lizidev

full member

Activity: 154

Merit: 100

Quote from: tonych on February 06, 2017, 04:03:01 AM

Quote from: francisthecrusher on February 05, 2017, 10:15:24 PM

I read those sections, but (the way I understand it at least) at some point the network still relies on trusted nodes to function, leaving it wide open to sybil attacks.

Could you be more specific please, how would you sybil attack?

Dev:

Code:

Could not sent payment:know bad

Why send is so unstable,It have a lot of bugs.

SatoNatomato

sr. member

Activity: 378

Merit: 250

@tonych, concerning nwjs and google requests, the proxy-to 127.7.7.7 solution, to make it better, can the wallet listen on 127.7.7.7:9989 for example, and have the proxy-set to that, with a username+password which is random for each start (proxy http://rand:[email protected]:9989 ) - then, the listener if it detects this username+password request on 9989 - log a warning/shutdown, huge fuckup is happpening? May be over-engineering though.

tonych

legendary

Activity: 965

Merit: 1033

Quote from: francisthecrusher on February 05, 2017, 10:15:24 PM

I read those sections, but (the way I understand it at least) at some point the network still relies on trusted nodes to function, leaving it wide open to sybil attacks.

Could you be more specific please, how would you sybil attack?

tonych

legendary

Activity: 965

Merit: 1033

Quote from: BTCspace on February 05, 2017, 07:06:04 PM

Hi
tonych

maybe you can ask poloniex list byteball, so we can spread byteball to more people, as an developer you request counter more weight than community members.

thank you

here is the link:

https://poloniex.com/coinRequest

Requested a couple of times, no response so far. Maybe they wait for more votes?

kola-schaar

sr. member

Activity: 336

Merit: 260

Quote from: btw50 on February 06, 2017, 02:17:25 AM

In the second round, we'll distribute as much as is linked and calculated by the above rules, the exact % is not known in advance.

could it be 10% at second round ?

No

1. BTC -> Byte
=> estimated ~100000 BTC linked (at 2. round) => 6250 GByte distributed

2. Byte -> Byte
=> 100000 GBytes (10% from the first round) => 10000 GBytes distributed

3. Total
Total: 16250 GBytes distributed at 2. round => 16250/1000000 = 1,6 %

4. Total distributed 1. + 2. round
11.6 % or 100000 (1. round) + 16250 (2. round) = 116250 Gbytes

SatoNatomato

sr. member

Activity: 378

Merit: 250

Quote from: lizidev on February 05, 2017, 11:53:55 PM

Quote from: escapefrom3dom on February 05, 2017, 09:19:19 PM

Quote from: francisthecrusher on February 05, 2017, 09:05:41 PM

From the Whitepaper:

Quote

Reliance on witnesses is what makes Byteball rooted in the real world.

Reading through the Whitepaper it seems that the devs took Bob McElrath's "Braiding Bitcoin" idea and solved the consensus problem by using trusted nodes (like Ripple) instead of an algorithm.

So it's basically something like Ripple but using a DAG instead of sequential blocks.

Kudos for starting somewhere, but this isn't a decentralized solution and is vulnerable to sybil attacks.

in the parts 4. Double-spends / 5. The main chain / 6. Witnesses of the whitelist u can see reviews for these cases.

Does this project have a double-spends problem?

No.

@davidovski, all gmen have to do to take down bitcoin is at gunpoint threaten a few people who are running the miners. See Namecoin pool had over 50% hashpower for a while before people even noticed. Bitcoin is useful even to gmen and bankers so they dont take it down. Ina year or so most taxoffices would like to run their own witnesses or hubs. Like they run bitcoin full nodes today to inspect and find who needs to pay taxes. We still have blackbytes though. Wink

SatoNatomato

sr. member

Activity: 378

Merit: 250

Quote from: francisthecrusher on February 05, 2017, 09:05:41 PM

From the Whitepaper:

Quote

Reliance on witnesses is what makes Byteball rooted in the real world.

Reading through the Whitepaper it seems that the devs took Bob McElrath's "Braiding Bitcoin" idea and solved the consensus problem by using trusted nodes (like Ripple) instead of an algorithm.

So it's basically something like Ripple but using a DAG instead of sequential blocks.

Kudos for starting somewhere, but this isn't a decentralized solution and is vulnerable to sybil attacks.

Hello Come-from-Beyonds sockpuppet.

Nice trolling.

To all reading except the troll:

Byteball is decentralized, trustless between users/nodes, and each user/node must trust his selection of witnesses.

This is no diffrent than trusting bitcoin miners will continue their operations and bitcoin node operators. The worst that could happen if witnesses misbehave is they are replaced.

Byteball is sybil resistant, you cant do any damage by spawning millions of wallets or fake users. You can spawn a witness but it will only loose bytes as nobody has it as its selecion. You cant even replace all the 12 witnesses with fake ones.

SatoNatomato

sr. member

Activity: 378

Merit: 250

Quote from: tonych on February 05, 2017, 06:50:20 PM

Quote from: SatoNatomato on February 05, 2017, 04:13:14 PM

edit2: if using the chromiu-args proxy workaround, make it something else than 127.0.0.1, like 127.6.6.6 to avoid more other problems.

What other problems and how doing this would avoid them?

people have other services bound to 127.0.0.1 listening and think theyre safe. Developers of those services think hey its unreachable. But if you set proxy to it, you allow any other exploits or mistakes in wallet to affect those services.

There has been examples of webpages getting posibility to send requests to 127.0.0.1 exploiting all kinds of daemons listening there

Defense in depth..

vlom

legendary

Activity: 1498

Merit: 1117

Quote from: scum on February 05, 2017, 05:23:54 PM

Quote from: vlom on February 05, 2017, 03:38:28 PM

Quote from: tonych on February 03, 2017, 06:50:51 PM

Quote from: vlom on February 03, 2017, 01:28:36 PM

why does the OS X app try to connect to google?

plus.google.com TCP-Port 443 (https)

What makes you think so?
There are no references to any sites (except the default hub) in the source code.

because little snitch tells my that the app wants to connect.

What program is your little snitch? It's so useful I want to install it on my computer.

this is little snitch:
https://www.obdev.at/products/littlesnitch/index.html

As soon as you’re connected to the Internet, applications can potentially send whatever information they want to wherever they want. Sometimes they do this for good reason, on your explicit request. But often they don’t.

Little Snitch intercepts these unwanted connection attempts,
and lets you decide how to proceed.

btw50

member

Activity: 91

Merit: 10

In the second round, we'll distribute as much as is linked and calculated by the above rules, the exact % is not known in advance.

could it be 10% at second round ?

CryptKeeper

legendary

Activity: 2044

Merit: 1055

Quote from: davidoski on February 06, 2017, 12:33:08 AM

Witnesses are the single point of failure of the system. They essentially control the network and there are only 12 of them. You can imagine that if the rogue government (bankers or whoever) wants to take down the byteball system all they have to do is to take controll over 12 computers running witnesses nodes. This seems to be rather easy to do, especially at gunpoint. Moreover - this can be done without the rest of the network to even notice - if witnesses after being taken over by the rogue party are operated without interruption. Anybody who controls the 12 witnesses can do whatever he wants with the network - for example censor certain type of transactions. All of this is a contradiction to censor resistant trustless network that bitcoin is.

I can follow your arguments and respect your opinion. Bitcoin was created as a decentralized platform and that was a great invention - in the old days when everybody could easily take part in the consenus with their CPU or GPU miners, this system was still intact. But nowadays bitcoin has become a total different thing. Expensive asic miners drive bitcoin to centralization and the need for low energy costs favor some countries.

I will ask you a question: how many mining pools do you need to cross the 50% consensus barrier in bitcoin? I guess it's a lot less than 12.

johny08

legendary

Activity: 1045

Merit: 1000

Quote from: BTCspace on February 05, 2017, 07:06:04 PM

Hi
tonych

maybe you can ask poloniex list byteball, so we can spread byteball to more people, as an developer you request counter more weight than community members.

thank you

here is the link:

https://poloniex.com/coinRequest

what i know it already happened.

kola-schaar

sr. member

Activity: 336

Merit: 260

Quote from: tonych on February 05, 2017, 06:29:48 PM

Quote from: realbigs21024 on February 05, 2017, 05:57:25 PM

i just downloaded wallet and when it synced it shows 1531 bytes where did they come from. lol

Interesting, did you install the wallet before?

It's not what you think. No problem. He had asked for help - he got some Wink

Quote from: realbigs21024 on February 05, 2017, 08:18:57 AM

can someone please send me one so i can see if my wallet is good to go # KWGIYJOT4AHXTEJQUGFDTO3R4XDEKZOO thanks

davidoski

sr. member

Activity: 297

Merit: 250

Witnesses are the single point of failure of the system. They essentially control the network and there are only 12 of them. You can imagine that if the rogue government (bankers or whoever) wants to take down the byteball system all they have to do is to take controll over 12 computers running witnesses nodes. This seems to be rather easy to do, especially at gunpoint. Moreover - this can be done without the rest of the network to even notice - if witnesses after being taken over by the rogue party are operated without interruption. Anybody who controls the 12 witnesses can do whatever he wants with the network - for example censor certain type of transactions. All of this is a contradiction to censor resistant trustless network that bitcoin is.

lizidev

full member

Activity: 154

Merit: 100

Quote from: escapefrom3dom on February 05, 2017, 09:19:19 PM

Quote from: francisthecrusher on February 05, 2017, 09:05:41 PM

From the Whitepaper:

Quote

Reliance on witnesses is what makes Byteball rooted in the real world.

Reading through the Whitepaper it seems that the devs took Bob McElrath's "Braiding Bitcoin" idea and solved the consensus problem by using trusted nodes (like Ripple) instead of an algorithm.

So it's basically something like Ripple but using a DAG instead of sequential blocks.

Kudos for starting somewhere, but this isn't a decentralized solution and is vulnerable to sybil attacks.

in the parts 4. Double-spends / 5. The main chain / 6. Witnesses of the whitelist u can see reviews for these cases.

Does this project have a double-spends problem?

Topic: Obyte: Totally new consensus algorithm + private untraceable payments - page 908. (Read 1234271 times)