Bitcoin Forum
June 24, 2019, 04:33:42 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 [219] 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 ... 1093 »
  Print  
Author Topic: Obyte: Totally new consensus algorithm + private untraceable payments  (Read 1169339 times)
lenyro
Sr. Member
****
Offline Offline

Activity: 250
Merit: 250


View Profile
February 06, 2017, 01:58:28 AM
 #4361


I've been looking for days and did not find it.
What was the conversion rate at the first snapshot please ?
I mean the exact amount of bytes we've got per BTC linked.

EDIT : Thx freigeist

check my last post.. for about 700BTC, i got about 1012588898911 byteball.

you can calculate it.

too much digits for me to counter..


Is it 10215 GB BB? So you have 10% of total supply like waves had, do you have more than 10k btc bind to get so much coins?
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
escapefrom3dom
Sr. Member
****
Offline Offline

Activity: 896
Merit: 263



View Profile WWW
February 06, 2017, 02:02:12 AM
 #4362


I've been looking for days and did not find it.
What was the conversion rate at the first snapshot please ?
I mean the exact amount of bytes we've got per BTC linked.

EDIT : Thx freigeist

check my last post.. for about 700BTC, i got about 1012588898911 byteball.

you can calculate it.

too much digits for me to counter..


Is it 10215 GB BB? So you have 10% of total supply like waves had, do you have more than 10k btc bind to get so much coins?

i suppose some proof needed to make such statemets.

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
Anonymous and Untraceable
ANN  Whitepaper  Facebook  Twitter  Telegram  Discord 





      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
.
francisthecrusher
Member
**
Offline Offline

Activity: 60
Merit: 10


View Profile
February 06, 2017, 02:05:41 AM
 #4363

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.
escapefrom3dom
Sr. Member
****
Offline Offline

Activity: 896
Merit: 263



View Profile WWW
February 06, 2017, 02:19:19 AM
 #4364

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.

           ▀██▄ ▄██▀
            ▐█████▌
           ▄███▀███▄
         ▄████▄  ▀███▄
       ▄███▀ ▀██▄  ▀███▄
     ▄███▀  ▄█████▄  ▀███▄
   ▄███▀  ▄███▀ ▀███▄  ▀███▄
  ███▀  ▄████▌   ▐████▄  ▀███
 ███   ██▀  ██▄ ▄██  ▀██   ███
███   ███  ███   ███  ███   ███
███   ███   ███████   ███   ███
 ███   ███▄▄       ▄▄███   ███
  ███▄   ▀▀█████████▀▀   ▄███
   ▀████▄▄           ▄▄████▀
      ▀▀███████████████▀▀
DeepOnion
Anonymous and Untraceable
ANN  Whitepaper  Facebook  Twitter  Telegram  Discord 





      ▄▄██████████▄▄
    ▄███▀▀      ▀▀█▀   ▄▄
   ███▀              ▄███
  ███              ▄███▀   ▄▄
 ███▌  ▄▄▄▄      ▄███▀   ▄███
▐███  ██████   ▄███▀   ▄███▀
███▌ ███  ███▄███▀   ▄███▀
███▌ ███   ████▀   ▄███▀
███▌  ███   █▀   ▄███▀  ███
▐███   ███     ▄███▀   ███
 ███▌   ███  ▄███▀     ███
  ███    ██████▀      ███
   ███▄             ▄███
    ▀███▄▄       ▄▄███▀
      ▀▀███████████▀▀
.
francisthecrusher
Member
**
Offline Offline

Activity: 60
Merit: 10


View Profile
February 06, 2017, 03:15:24 AM
 #4365

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.

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. The whole point of Bitcoin of course is that no nodes are 'special'.

Here are some quotes from the whitepaper:

Quote
Total order is established by selecting a single chain on the DAG (the main chain) that is attracted to units signed by known users called witnesses.

Quote
some of the participants of our network are non-anonymous reputable people or companies who might have a long established reputation...we’ll call them witnesses.

Quote
a more practical approach to witness list management is tracking and somehow averaging the witness lists of a few “captains of industry”


lizidev
Full Member
***
Offline Offline

Activity: 154
Merit: 100



View Profile
February 06, 2017, 04:53:55 AM
 #4366

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?
davidoski
Sr. Member
****
Offline Offline

Activity: 297
Merit: 250



View Profile
February 06, 2017, 05:33:08 AM
 #4367

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.

Chancellor on brink of second bailout for banks
kola-schaar
Sr. Member
****
Offline Offline

Activity: 336
Merit: 260


View Profile
February 06, 2017, 06:45:09 AM
 #4368

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

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

Activity: 1042
Merit: 1000


View Profile
February 06, 2017, 06:46:00 AM
 #4369

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.
CryptKeeper
Legendary
*
Offline Offline

Activity: 1890
Merit: 1014


bitcoin and altcoin enthusiast


View Profile WWW
February 06, 2017, 07:09:36 AM
 #4370

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.

Follow me on twitter for the latest news on bitcoin and altcoins and I'll follow you back the same day!
Obyte - An open cryptocurrency platform ready for real world adoption
btw50
Member
**
Offline Offline

Activity: 91
Merit: 10


View Profile
February 06, 2017, 07:17:25 AM
 #4371


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 ?
vlom
Legendary
*
Offline Offline

Activity: 1344
Merit: 1105



View Profile WWW
February 06, 2017, 07:43:12 AM
 #4372

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.

|\¯¯ \   /¯¯/| |¯¯¯|__'  /¯¯,¯¯\     /¯¯\/¯ \'  
\  \__\/__/ /' |_____'| |\____ /|'  /__ (\/)__\
  '\|____ |/'   |_____'|  \|___ |/ °|___ |v|___|
    '                                             
    '         [/colo
SatoNatomato
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250


View Profile
February 06, 2017, 08:09:08 AM
 #4373

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..
SatoNatomato
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250


View Profile
February 06, 2017, 08:17:14 AM
 #4374

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
****
Offline Offline

Activity: 364
Merit: 250


View Profile
February 06, 2017, 08:27:51 AM
 #4375

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
kola-schaar
Sr. Member
****
Offline Offline

Activity: 336
Merit: 260


View Profile
February 06, 2017, 08:28:15 AM
 #4376


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
tonych
Hero Member
*****
Offline Offline

Activity: 875
Merit: 803


View Profile WWW
February 06, 2017, 08:58:45 AM
 #4377

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?

Simplicity is beauty
tonych
Hero Member
*****
Offline Offline

Activity: 875
Merit: 803


View Profile WWW
February 06, 2017, 09:03:01 AM
 #4378

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?

Simplicity is beauty
SatoNatomato
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250


View Profile
February 06, 2017, 09:18:20 AM
 #4379

@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:0m@127.7.7.7: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.
lizidev
Full Member
***
Offline Offline

Activity: 154
Merit: 100



View Profile
February 06, 2017, 09:24:25 AM
 #4380

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.
Pages: « 1 ... 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 [219] 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 ... 1093 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!