Bitcoin Forum
April 26, 2024, 04:30:14 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 [168] 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 ... 1126 »
  Print  
Author Topic: Obyte: Totally new consensus algorithm + private untraceable payments  (Read 1233955 times)
SatoNatomato
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
January 11, 2017, 12:18:57 PM
 #3341

Just created a thread,

Go here to send and receive kilobytes from fellow bitcointalkers.

https://bitcointalk.org/index.php?topic=1747361.new#new
1714149014
Hero Member
*
Offline Offline

Posts: 1714149014

View Profile Personal Message (Offline)

Ignore
1714149014
Reply with quote  #2

1714149014
Report to moderator
Be very wary of relying on JavaScript for security on crypto sites. The site can change the JavaScript at any time unless you take unusual precautions, and browsers are not generally known for their airtight security.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714149014
Hero Member
*
Offline Offline

Posts: 1714149014

View Profile Personal Message (Offline)

Ignore
1714149014
Reply with quote  #2

1714149014
Report to moderator
CryptKeeper
Legendary
*
Offline Offline

Activity: 2044
Merit: 1055



View Profile
January 11, 2017, 12:40:17 PM
 #3342

Better go to slack for trading!

There is a slack channel #trading for Bytes and #trading_blackbytes for Blackbytes, please go there if you want to buy, sell, exchange Bytes and Blackbytes or want to speculate about the price!  Grin

There's also an automated order book at #book (Bytes asks and bids only):
Quote
List of commands:
ASKS
BIDS
ASK <BTC> <GB>
BID <BTC> <GB>
REMOVE ASK
REMOVE BID

Please keep this in mind for your own safety:

Quote
Little guide for Byteball trading

This slack channel is for discussing Byteball trading and for organizing such trades. Please be aware that at the moment, the only way to trade safely is through a reputable escrow middleman! Even if you think you know the guy who you want to trade with, you should better trade through an escrow! We've already seen lots of scammers who try to impersonate well-known community members. So proceed with due diligence and always make sure that you are dealing with the right person, especially your escrow middleman. Only use registered escrow services and compare the usernames and bitcoin addresses carefully before you send someone your precious coins!

Registered escrow services:

@yassinnxt
Registered escrow bitcoin address: 153tSmxbKfby652LUyYdYEZhoxY9RzHYrz
Fee: 1% in BTC (from Byteball buyer)
(approx. 2700 BTC escrowed so far)

@seccour
Registered escrow bitcoin address: 1Hx3kxKbYyNgGyqzLB5Qw8BA8dZbuu1Xjn
Fee: none (tips accepted)
(over 500 BTC escrowed so far)

@martis
Registered escrow bitcoin address: 1pMPHbinYokoXEDav5J3tkto14rxBSwx9
Fee: 1% in BTC (split 50/50 between buyer and seller)

Get your slack invite here: http://slack.byteball.org/

Follow me on twitter! I'm a private Bitcoin and altcoin hodler. Giving away crypto for free on my Twitter feed!
CryptKeeper
Legendary
*
Offline Offline

Activity: 2044
Merit: 1055



View Profile
January 11, 2017, 01:42:58 PM
 #3343

Just created a thread,

Go here to send and receive kilobytes from fellow bitcointalkers.

https://bitcointalk.org/index.php?topic=1747361.new#new

Good idea! Thanks for creating such thread.

 Smiley  Smiley  Smiley

Follow me on twitter! I'm a private Bitcoin and altcoin hodler. Giving away crypto for free on my Twitter feed!
yvv
Legendary
*
Offline Offline

Activity: 1344
Merit: 1000

.


View Profile WWW
January 11, 2017, 02:07:53 PM
 #3344

@tonych

Why don't you change the distribution such that it rewards actual users of byteball? You could code a smart contract such that every tenth transaction fee is redeemed from undistributed reserve. This way the amount of bytes in circulation would grow with the same pace as usage.


This proposal is not bad at all. But one big agreement must be:

The new coins only goes to new users. The problem: i could make 10k adresses to reach many byteballs. So this proposal needs more clarifications.




My idea is to reward frequent users. Right now, everybody can buy bytes at the market to pay tx fees. Let everybody pay first, than make a snapshot every so often, and redeem each address a fraction of fees which it payed (e.g 10%). This way it does not matter how many addresses one individual has, he still needs to pay first to be redeemed later. And this puts whales out of the loop unless they become frequent users.

For example, exchanges will be frequent users and get redeemed a lot, but this will benefit their users, since exchange can charge less fees.

Given that most transactions are 500-1000 bytes, only 10% is redeemed, and there are 8.8 * 1014 still undistributed bytes, if you do the math, you won't like this idea yourself.

I don't see where this number comes from. All of bytes will be distributed this way eventually. If you want to distribute them faster, you could redeem 90% of fees.

.
kaicrypzen
Hero Member
*****
Offline Offline

Activity: 1344
Merit: 656



View Profile
January 11, 2017, 03:07:11 PM
 #3345

Given that most transactions are 500-1000 bytes, only 10% is redeemed, and there are 8.8 * 1014 still undistributed bytes, if you do the math, you won't like this idea yourself.

I don't see where this number comes from. All of bytes will be distributed this way eventually. If you want to distribute them faster, you could redeem 90% of fees.

8.8*1014 is the number of remaining bytes to be distributed: In percentage, that is 100-10(first round)-1(tonych's)-1(first 100m users) = 88% of 1015 which is 8.8*1014. Distributing that amount only by redeeming a fraction of the fee would take quite some time.

SatoNatomato
Sr. Member
****
Offline Offline

Activity: 378
Merit: 250


View Profile
January 11, 2017, 03:07:51 PM
 #3346

@tonych

Why don't you change the distribution such that it rewards actual users of byteball? You could code a smart contract such that every tenth transaction fee is redeemed from undistributed reserve. This way the amount of bytes in circulation would grow with the same pace as usage.


This proposal is not bad at all. But one big agreement must be:

The new coins only goes to new users. The problem: i could make 10k adresses to reach many byteballs. So this proposal needs more clarifications.




My idea is to reward frequent users. Right now, everybody can buy bytes at the market to pay tx fees. Let everybody pay first, than make a snapshot every so often, and redeem each address a fraction of fees which it payed (e.g 10%). This way it does not matter how many addresses one individual has, he still needs to pay first to be redeemed later. And this puts whales out of the loop unless they become frequent users.

For example, exchanges will be frequent users and get redeemed a lot, but this will benefit their users, since exchange can charge less fees.

Given that most transactions are 500-1000 bytes, only 10% is redeemed, and there are 8.8 * 1014 still undistributed bytes, if you do the math, you won't like this idea yourself.

I don't see where this number comes from. All of bytes will be distributed this way eventually. If you want to distribute them faster, you could redeem 90% of fees.

The problem exists if you get more bytes from the undistributed store than what the fee would have costed.

So average transaction cost 588bytes - if every 10th transaction would earn me more than 5880 bytes, someone would just write a short script to send transactions between his/her wallet - and siphon off all the undistributed bytes!

What is OK is to just "write-off" the 10th (or one randomly selected transaction between 10 - 64), no matter its cost but capped to 10kb, to be given to sender from undistributed reserve. This would mean, most transactions cost as protocol says - but sometimes you get lucky and have your transaction payed for by the undistributed reserve. This scheme would just lower the cost of doing transactions in the growing/initial phase of byteball. Its not a method of distribution of all bytes.
temmuz
Sr. Member
****
Offline Offline

Activity: 784
Merit: 425


View Profile
January 11, 2017, 03:17:57 PM
 #3347

Is following a very successful course. From 0,015 to 0,25 I think when you think about entering the bigger stock market for the first stage.
yvv
Legendary
*
Offline Offline

Activity: 1344
Merit: 1000

.


View Profile WWW
January 11, 2017, 03:56:45 PM
 #3348

Given that most transactions are 500-1000 bytes, only 10% is redeemed, and there are 8.8 * 1014 still undistributed bytes, if you do the math, you won't like this idea yourself.

I don't see where this number comes from. All of bytes will be distributed this way eventually. If you want to distribute them faster, you could redeem 90% of fees.

8.8*1014 is the number of remaining bytes to be distributed: In percentage, that is 100-10(first round)-1(tonych's)-1(first 100m users) = 88% of 1015 which is 8.8*1014. Distributing that amount only by redeeming a fraction of the fee would take quite some time.

I see. It will take around 10 trillion transactions to distribute all bytes this way. Is it too slow?

.
spark.bet
Full Member
***
Offline Offline

Activity: 155
Merit: 100


View Profile
January 11, 2017, 06:48:58 PM
 #3349

If all distributions give 0.1 new bytes for every 1 byte.
You have 10 GB and there are still:

1 distribution, you are going to have 11GB
2 distribution, you are going to have 12.1GB
3 distribution, you are going to have 13.31GB
4 distribution, you are going to have 14.64GB
5 distribution, you are going to have 16.10GB
6 distribution, you are going to have 17.71GB
7 distribution, you are going to have 19.48GB
8 distribution, you are going to have 19.48GB
9 distribution, you are going to have 21.43GB
10 distribution, you are going to have 23.57GB
11 distribution, you are going to have 25.93GB
12 distribution, you are going to have 28.53GB
13 distribution, you are going to have 31.38GB
14 distribution, you are going to have 34.52GB
15 distribution, you are going to have 37.97GB
kaicrypzen
Hero Member
*****
Offline Offline

Activity: 1344
Merit: 656



View Profile
January 11, 2017, 07:16:52 PM
 #3350

Given that most transactions are 500-1000 bytes, only 10% is redeemed, and there are 8.8 * 1014 still undistributed bytes, if you do the math, you won't like this idea yourself.

I don't see where this number comes from. All of bytes will be distributed this way eventually. If you want to distribute them faster, you could redeem 90% of fees.

8.8*1014 is the number of remaining bytes to be distributed: In percentage, that is 100-10(first round)-1(tonych's)-1(first 100m users) = 88% of 1015 which is 8.8*1014. Distributing that amount only by redeeming a fraction of the fee would take quite some time.

I see. It will take around 10 trillion transactions to distribute all bytes this way. Is it too slow?

I actually have no idea about how many transactions are done daily (or on a regular basis), to assess if it would be too slow ... Does anyone know the number of transactions per day or how to estimate that number?

tonych (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1008


View Profile WWW
January 11, 2017, 07:28:20 PM
 #3351

Two news for today.

TOR support

Now all server based Byteball nodes can connect through TOR.  TOR support in GUI wallets will be added in one of the future releases.  TOR is supported in:

- merchant https://github.com/byteball/byteball-merchant
- headless wallet https://github.com/byteball/headless-byteball

Since Byteball merchants operate in chat interface (unlike web sites), they already don't have to accept incoming connections, therefore don't have to have a publicly known IP address, and TOR support means that they also can hide their IP addresses when making outgoing connections.  This allows them to be completely hidden.  At the same time, customers don't have to use TOR to chat with the merchant bot.

Being able to completely hide one's IP address is even more important for server based wallets that may store large amounts of funds online and be a lucrative target for attackers.  With the IP address hidden, the attackers simply do not know what server to attack, or it is much harder to learn.  So, for headless wallets, TOR allows to achieve better security, not just anonymity.  This is used in the new product which is the subject of our second news today.

Exchange bot that allows to exchange BTC to Bytes and vice versa

The exchange is as easy to use as ShapeShift.  No registration required.  To buy Bytes, you start the chat, send Bitcoins, and a few minutes later you receive the Bytes.  Same for selling Bytes.  You can also create a pending order and hope to get a better deal.



The bot is running on testnet now, see the link at https://byteball.org/testnet.html (you'll need a separate wallet for testnet).

The exchange is trustful, it holds customers' funds, even if it is for a short time.  To minimize risks, the exchange runs through TOR, which makes its IP address unknown to the attackers.  Since it operates in chat and doesn't have to accept incoming connections, you can run the exchange bot even in your bedroom, with the added advantage of being behind NAT.

As another measure to minimize its liabilities and the associated risks, the exchange bot discourages pending orders that are too far from the market price by allowing withdrawals only in the opposite currency and by allowing to modify the order's price only when it accelerates its execution.

Full source code and install instructions are at https://github.com/byteball/btc-exchange.

Please test the exchange on testnet by clicking its link at https://byteball.org/testnet.html, any feedback is appreciated.

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

Activity: 504
Merit: 250



View Profile
January 11, 2017, 07:28:50 PM
 #3352


Is there a reason for the  specific number 2.1111 blackbyte for 1 byteball?
Why not just 2 for 1.

I think this is because of the denominators. Byteballs can be spent at any amount, not blackbytes. Blackbytes are like money, you can spend only use these denominators:

{denomination: 1, count_coins: 10,000,000,000},
{denomination: 2, count_coins: 20,000,000,000},
{denomination: 5, count_coins: 10,000,000,000},
{denomination: 10, count_coins: 10,000,000,000},
{denomination: 20, count_coins: 20,000,000,000},
{denomination: 50, count_coins: 10,000,000,000},
{denomination: 100, count_coins: 10,000,000,000},
{denomination: 200, count_coins: 20,000,000,000},
{denomination: 500, count_coins: 10,000,000,000},
{denomination: 1000, count_coins: 10,000,000,000},
{denomination: 2000, count_coins: 20,000,000,000},
{denomination: 5000, count_coins: 10,000,000,000},
{denomination: 10000, count_coins: 10,000,000,000},
{denomination: 20000, count_coins: 20,000,000,000},
{denomination: 50000, count_coins: 10,000,000,000},
{denomination: 100000, count_coins: 10,000,000,000}

That's how 2.111x10^15 come from.
strasboug
Sr. Member
****
Offline Offline

Activity: 504
Merit: 250



View Profile
January 11, 2017, 07:30:27 PM
 #3353

Two news for today.

TOR support

Now all server based Byteball nodes can connect through TOR.  TOR support in GUI wallets will be added in one of the future releases.  TOR is supported in:

- merchant https://github.com/byteball/byteball-merchant
- headless wallet https://github.com/byteball/headless-byteball

Since Byteball merchants operate in chat interface (unlike web sites), they already don't have to accept incoming connections, therefore don't have to have a publicly known IP address, and TOR support means that they also can hide their IP addresses when making outgoing connections.  This allows them to be completely hidden.  At the same time, customers don't have to use TOR to chat with the merchant bot.

Being able to completely hide one's IP address is even more important for server based wallets that may store large amounts of funds online and be a lucrative target for attackers.  With the IP address hidden, the attackers simply do not know what server to attack, or it is much harder to learn.  So, for headless wallets, TOR allows to achieve better security, not just anonymity.  This is used in the new product which is the subject of our second news today.

Exchange bot that allows to exchange BTC to Bytes and vice versa

The exchange is as easy to use as ShapeShift.  No registration required.  To buy Bytes, you start the chat, send Bitcoins, and a few minutes later you receive the Bytes.  Same for selling Bytes.  You can also create a pending order and hope to get a better deal.



The bot is running on testnet now, see the link at https://byteball.org/testnet.html (you'll need a separate wallet for testnet).

The exchange is trustful, it holds customers' funds, even if it is for a short time.  To minimize risks, the exchange runs through TOR, which makes its IP address unknown to the attackers.  Since it operates in chat and doesn't have to accept incoming connections, you can run the exchange bot even in your bedroom, with the added advantage of being behind NAT.

As another measure to minimize its liabilities and the associated risks, the exchange bot discourages pending orders that are too far from the market price by allowing withdrawals only in the opposite currency and by allowing to modify the order's price only when it accelerates its execution.

Full source code and install instructions are at https://github.com/byteball/btc-exchange.

Please test the exchange on testnet by clicking its link at https://byteball.org/testnet.html, any feedback is appreciated.


Wonderful news, does the trading bot works for blackbytes too? I am interested in trading some blackbytes for white bytes...
amacar1
Hero Member
*****
Offline Offline

Activity: 707
Merit: 501


View Profile
January 11, 2017, 07:47:13 PM
 #3354

...

Wonderful news, does the trading bot works for blackbytes too? I am interested in trading some blackbytes for white bytes...
tonych wrote that trading bot works only on testnet right now, so no, trading blackbytes for byteballs is not possible.
tonych (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1008


View Profile WWW
January 11, 2017, 07:50:16 PM
 #3355

Wonderful news, does the trading bot works for blackbytes too? I am interested in trading some blackbytes for white bytes...

It works for bytes only.
We'll have a bytes-to-blackbytes P2P exchange on the network.

Simplicity is beauty
kola-schaar
Sr. Member
****
Offline Offline

Activity: 336
Merit: 260


View Profile
January 11, 2017, 08:13:28 PM
 #3356

I don't like cheerleading..
Hmmm.. I miss the words… think I have to speak again with my bank   Cool
yvv
Legendary
*
Offline Offline

Activity: 1344
Merit: 1000

.


View Profile WWW
January 11, 2017, 10:07:43 PM
 #3357

Wonderful news, does the trading bot works for blackbytes too? I am interested in trading some blackbytes for white bytes...

It works for bytes only.
We'll have a bytes-to-blackbytes P2P exchange on the network.

These are excellent news.

.
Yaremi
Legendary
*
Offline Offline

Activity: 1960
Merit: 1126


View Profile WWW
January 11, 2017, 10:19:36 PM
 #3358

1. Byteball Private untraceable payments more anonymous than Monero, DASH and ZCASH? I'm right?
2. Is possible start Dice via chat bot?

Thanks!

Зaлeтaй в нaш чaт http://allcrypto.chat/
crypt0hash
Newbie
*
Offline Offline

Activity: 57
Merit: 0


View Profile
January 12, 2017, 12:17:05 AM
 #3359


TOR support

Exchange bot that allows to exchange BTC to Bytes and vice versa

The bot is running on testnet now

Great features, thank you tonych!
galaxy
Member
**
Offline Offline

Activity: 109
Merit: 10


View Profile
January 12, 2017, 01:08:15 AM
 #3360

Is there a trading thread?
Pages: « 1 ... 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 [168] 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 ... 1126 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!