Bitcoin Forum
April 25, 2024, 08:04:35 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 [81] 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 ... 1126 »
  Print  
Author Topic: Obyte: Totally new consensus algorithm + private untraceable payments  (Read 1233954 times)
journeym@n
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
December 10, 2016, 09:25:24 PM
 #1601

Any rough statistics of how many users will be connecting their BTC to Bytball address?

http://transition.byteball.org/

looks like some big fishes linked their BTC. Do we have a count how much BTCs are already linked?

Currently there are 8706.44455897 BTC that you can find on top of the statistic page.

I was originally going to link my Bitcoin address to get some Byteballs but after looking at the website that you postsed in regards to how many Bitcoin is linked and how many per address it seems very much unviable for little everyday joes which most of us are, there is one user with 2578.76557524 BTC Linked to his Byteball address..... Seems like whales already control this coin before release.

As long as a single bitcoin (of all that currently exist) is not included in this initial distribution, we are all undoubtedly advantaged despite how many BTC we have. And in reality, >95% of BTC holders will not take part in this initial distribution. Thus, I do not fully understand your reasoning.

BTW, that 2xxx BTC account is some sort of joint account.. Komodo related, whatever that is.. I was absent for too long
1714032275
Hero Member
*
Offline Offline

Posts: 1714032275

View Profile Personal Message (Offline)

Ignore
1714032275
Reply with quote  #2

1714032275
Report to moderator
1714032275
Hero Member
*
Offline Offline

Posts: 1714032275

View Profile Personal Message (Offline)

Ignore
1714032275
Reply with quote  #2

1714032275
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714032275
Hero Member
*
Offline Offline

Posts: 1714032275

View Profile Personal Message (Offline)

Ignore
1714032275
Reply with quote  #2

1714032275
Report to moderator
1714032275
Hero Member
*
Offline Offline

Posts: 1714032275

View Profile Personal Message (Offline)

Ignore
1714032275
Reply with quote  #2

1714032275
Report to moderator
1714032275
Hero Member
*
Offline Offline

Posts: 1714032275

View Profile Personal Message (Offline)

Ignore
1714032275
Reply with quote  #2

1714032275
Report to moderator
zanzibar
Hero Member
*****
Offline Offline

Activity: 715
Merit: 500



View Profile
December 10, 2016, 09:32:57 PM
 #1602

Meaning? Komodo is claiming some bytes on Dec 25?

Yes, Komodo is another shit pump and dump by James, I'm sure he'll move on to something else before it's finished with it, like every project before. And he'll now own most of Byteball and yes, he'll dump it as soon as it's on exchanges so he can "fund" himself.
ICOcountdown.com
Hero Member
*****
Offline Offline

Activity: 1008
Merit: 500


View Profile WWW
December 10, 2016, 09:45:57 PM
 #1603

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

LiQio
Legendary
*
Offline Offline

Activity: 1181
Merit: 1002



View Profile
December 10, 2016, 10:02:11 PM
 #1604

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

That's the risk that tonych wanted to take. It is an intrinsic (and as stated IMO deadly) risk of the distribution design.
Therefore no censorship.

spud21
Sr. Member
****
Offline Offline

Activity: 342
Merit: 250



View Profile
December 10, 2016, 10:09:30 PM
 #1605

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

I agree addresses containing funds from giant ICOs need excluding to prevent them damaging the byteball market. I searched for the lisk ICO Bitcoin address without luck. That ICO raised 14000 Bitcoins, and waves raised 29636 Bitcoins. If we could compile a list of Bitcoin addresses holding Bitcoins from all giant ICOs it would give the dev the option of easily excluding them all.

Does anyone have links to giant ICO Bitcoin funds addresses?
kaicrypzen
Hero Member
*****
Offline Offline

Activity: 1344
Merit: 656



View Profile
December 10, 2016, 10:14:45 PM
 #1606

Why would lowering the micropayment be riskier than with the current micropayments? (because they would be easily spotted?)

Because the attack would become cheaper, hence worthwhile.

mmmm, in my opinion the attack is already worthwhile, anyway such an attack won't succeed unless the attackee is not vigilant and doesn't double check their address (as the bot instructs them), so why not lower it if it permits to filter out exchanges addresses at the detection process (not requiring you to check suspect addresses)?

People do make mistakes, and having to be overly vigilant scares them off.  I'd rather have a more comfortable environment for the entire process.
The attacker's ROI depends on 3 factors:
- % of people who do not check that the address is theirs after receiving a second notification "Received your payment from ..." (the attacker's microtransaction is almost certainly later than the legitimate one)
- average balance of such users
- cost of attacking, which is the average amount of the microtransaction
By lowering the cost, we turn the ROI at some point from negative to positive.

I see your point. If you are comfortable with filtering out exchanges addresses after adding them and then investigating them, then there is no need to lower the micropayment. Yet, I still think lowering it would easily filter any exchange address out as the transaction won't be possible to begin with. (and if I were an attacker, paying (n times) 0.000x instead of 0.0000x wouldn't hurt my ROI that much Smiley).

tonych (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1008


View Profile WWW
December 10, 2016, 10:17:40 PM
 #1607

Is it possible to use different BB address for every BTC address? I tried generating new BB address and bot still asks to sign previous one.

Only if you link from different devices, e.g. desktop and Android.

Do you plan to enable this option? Some people have multiple addresses for a reason. It might be irrelevant at this point but BTC is hopefully here to stay. Addresses being tied by common BB address in your transition table do unnecessarily provide additional info to outside entities.

Fair enough.
Now you can tell the bot your another BB address and then link the next Bitcoin address.
To force generation of a new BB address, exit the chat using "< Back" button in the topbar, then return to the chat.

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

Activity: 416
Merit: 250



View Profile
December 10, 2016, 10:32:04 PM
 #1608

cek my pm sir

           
          
▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰
WORLDWIDE VIRTUAL MOBILE OPERATOR
▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰ ▰
Twitter   ❐ Facebook   ❐ Youtube   ❐ Linkedin    ❐ Telegram  
▄███████████████▄
██           ████
██    ▄▄▄▄▄    ██
██             ██
██             ██
██    ▀▀▀▀▀    ██
██             ██
▀███████████████▀
  Whitepaper
        ( eng ) ││ ( rus )
▄███████████████▄
███████   ███████
██████     ██████
███████   ███████
███████▄ ▄███████
█████████████████
███████   ███████
▀███████████████▀
Announcement
  Thread in: ( eng ) ││ ( rus )
Seccour
Legendary
*
Offline Offline

Activity: 1619
Merit: 1004


Bitcoiner, Crypto-anarchist and Cypherpunk.


View Profile
December 10, 2016, 10:33:51 PM
 #1609

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

I agree addresses containing funds from giant ICOs need excluding to prevent them damaging the byteball market. I searched for the lisk ICO Bitcoin address without luck. That ICO raised 14000 Bitcoins, and waves raised 29636 Bitcoins. If we could compile a list of Bitcoin addresses holding Bitcoins from all giant ICOs it would give the dev the option of easily excluding them all.

Does anyone have links to giant ICO Bitcoin funds addresses?

Censorship of some Bitcoin addresses will done more harm than good to Byteball. The Komodo team by saying that they will collect byteball just make a big promotion of Byteball to their community.

And there is still time until the distribution.

animalroam
Legendary
*
Offline Offline

Activity: 1073
Merit: 1000


View Profile
December 10, 2016, 10:35:54 PM
 #1610

Why would lowering the micropayment be riskier than with the current micropayments? (because they would be easily spotted?)

Because the attack would become cheaper, hence worthwhile.

mmmm, in my opinion the attack is already worthwhile, anyway such an attack won't succeed unless the attackee is not vigilant and doesn't double check their address (as the bot instructs them), so why not lower it if it permits to filter out exchanges addresses at the detection process (not requiring you to check suspect addresses)?

People do make mistakes, and having to be overly vigilant scares them off.  I'd rather have a more comfortable environment for the entire process.
The attacker's ROI depends on 3 factors:
- % of people who do not check that the address is theirs after receiving a second notification "Received your payment from ..." (the attacker's microtransaction is almost certainly later than the legitimate one)
- average balance of such users
- cost of attacking, which is the average amount of the microtransaction
By lowering the cost, we turn the ROI at some point from negative to positive.

I see your point. If you are comfortable with filtering out exchanges addresses after adding them and then investigating them, then there is no need to lower the micropayment. Yet, I still think lowering it would easily filter any exchange address out as the transaction won't be possible to begin with. (and if I were an attacker, paying (n times) 0.000x instead of 0.0000x wouldn't hurt my ROI that much Smiley).

I agree, but instead of manual filtering, maybe requiring signatures on an amount above X would be beneficial since it wouldn't be hurting anyone; those who are not good at technology usually own less Bitcoin. Plus, it would greatly reduce the effect of those who are putting in exchange/joint wallet addresses. That way, it would only exclude those who cheat the system.
ICOcountdown.com
Hero Member
*****
Offline Offline

Activity: 1008
Merit: 500


View Profile WWW
December 10, 2016, 10:37:12 PM
 #1611

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

I agree addresses containing funds from giant ICOs need excluding to prevent them damaging the byteball market. I searched for the lisk ICO Bitcoin address without luck. That ICO raised 14000 Bitcoins, and waves raised 29636 Bitcoins. If we could compile a list of Bitcoin addresses holding Bitcoins from all giant ICOs it would give the dev the option of easily excluding them all.

Does anyone have links to giant ICO Bitcoin funds addresses?

Censorship of some Bitcoin addresses will done more harm than good to Byteball. The Komodo team by saying that they will collect byteball just make a big promotion of Byteball to their community.

And there is still time until the distribution.

That is a fair comment with regard to marketing and promotion. However if continual market extraction occurs it could be very negative. I don't think there is a right answer in this case but I'm happy that other projects are getting involved.

Seccour
Legendary
*
Offline Offline

Activity: 1619
Merit: 1004


Bitcoiner, Crypto-anarchist and Cypherpunk.


View Profile
December 10, 2016, 10:38:34 PM
 #1612

Why would lowering the micropayment be riskier than with the current micropayments? (because they would be easily spotted?)

Because the attack would become cheaper, hence worthwhile.

mmmm, in my opinion the attack is already worthwhile, anyway such an attack won't succeed unless the attackee is not vigilant and doesn't double check their address (as the bot instructs them), so why not lower it if it permits to filter out exchanges addresses at the detection process (not requiring you to check suspect addresses)?

People do make mistakes, and having to be overly vigilant scares them off.  I'd rather have a more comfortable environment for the entire process.
The attacker's ROI depends on 3 factors:
- % of people who do not check that the address is theirs after receiving a second notification "Received your payment from ..." (the attacker's microtransaction is almost certainly later than the legitimate one)
- average balance of such users
- cost of attacking, which is the average amount of the microtransaction
By lowering the cost, we turn the ROI at some point from negative to positive.

I see your point. If you are comfortable with filtering out exchanges addresses after adding them and then investigating them, then there is no need to lower the micropayment. Yet, I still think lowering it would easily filter any exchange address out as the transaction won't be possible to begin with. (and if I were an attacker, paying (n times) 0.000x instead of 0.0000x wouldn't hurt my ROI that much Smiley).

I agree, but instead of manual filtering, maybe requiring signatures on an amount above X would be beneficial since it wouldn't be hurting anyone; those who are not good at technology usually own less Bitcoin. Plus, it would greatly reduce the effect of those who are putting in exchange/joint wallet addresses. That way, it would only exclude those who cheat the system.

Could we just ask big exchanges to claim and distribute their Byteball to their users ? Like Poloniex and others exchange did with Ardor distribution ?

Because really that would make everyone life easier and more people will be aware about Byteball.

journeym@n
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
December 10, 2016, 10:46:13 PM
 #1613

Fair enough.
Now you can tell the bot your another BB address and then link the next Bitcoin address.
To force generation of a new BB address, exit the chat using "< Back" button in the topbar, then return to the chat.

Thank you
animalroam
Legendary
*
Offline Offline

Activity: 1073
Merit: 1000


View Profile
December 10, 2016, 11:05:52 PM
 #1614

Why would lowering the micropayment be riskier than with the current micropayments? (because they would be easily spotted?)

Because the attack would become cheaper, hence worthwhile.

mmmm, in my opinion the attack is already worthwhile, anyway such an attack won't succeed unless the attackee is not vigilant and doesn't double check their address (as the bot instructs them), so why not lower it if it permits to filter out exchanges addresses at the detection process (not requiring you to check suspect addresses)?

People do make mistakes, and having to be overly vigilant scares them off.  I'd rather have a more comfortable environment for the entire process.
The attacker's ROI depends on 3 factors:
- % of people who do not check that the address is theirs after receiving a second notification "Received your payment from ..." (the attacker's microtransaction is almost certainly later than the legitimate one)
- average balance of such users
- cost of attacking, which is the average amount of the microtransaction
By lowering the cost, we turn the ROI at some point from negative to positive.

I see your point. If you are comfortable with filtering out exchanges addresses after adding them and then investigating them, then there is no need to lower the micropayment. Yet, I still think lowering it would easily filter any exchange address out as the transaction won't be possible to begin with. (and if I were an attacker, paying (n times) 0.000x instead of 0.0000x wouldn't hurt my ROI that much Smiley).

I agree, but instead of manual filtering, maybe requiring signatures on an amount above X would be beneficial since it wouldn't be hurting anyone; those who are not good at technology usually own less Bitcoin. Plus, it would greatly reduce the effect of those who are putting in exchange/joint wallet addresses. That way, it would only exclude those who cheat the system.

Could we just ask big exchanges to claim and distribute their Byteball to their users ? Like Poloniex and others exchange did with Ardor distribution ?

Because really that would make everyone life easier and more people will be aware about Byteball.

I highly doubt all exchanges would agree to do that. Even the small exchanges have considerable amounts of BTC in their wallets.
tonych (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1008


View Profile WWW
December 10, 2016, 11:31:13 PM
 #1615

Personally I would like there to be a vote if this address can be honoured, since I don't think it's beneficial to the network we are creating here. It seems more like they want more of a cash injection into there own project.

Ultimately I believe moves like this will damage our market and make it less liquid and more prone to damage in long term along with holding up a large portion of the network.

If you agree with these sentiments it is very important at this stage to make your voice known.  Cool

I agree addresses containing funds from giant ICOs need excluding to prevent them damaging the byteball market. I searched for the lisk ICO Bitcoin address without luck. That ICO raised 14000 Bitcoins, and waves raised 29636 Bitcoins. If we could compile a list of Bitcoin addresses holding Bitcoins from all giant ICOs it would give the dev the option of easily excluding them all.

Does anyone have links to giant ICO Bitcoin funds addresses?

Censorship of some Bitcoin addresses will done more harm than good to Byteball. The Komodo team by saying that they will collect byteball just make a big promotion of Byteball to their community.

And there is still time until the distribution.

That is a fair comment with regard to marketing and promotion. However if continual market extraction occurs it could be very negative. I don't think there is a right answer in this case but I'm happy that other projects are getting involved.

Nobody here wants the network to be controlled by superwhales, neither do I.  One strategy to avoid that is trying to shoot them, however I believe letting the whales dilute other whales would work better, because it would also make us bigger.  I like ICO funds in particular, because, as Seccour says above, their participation is an endorsement, which is going to be heard by their communities.  Synereo and BlockPay are going to participate too.

Simplicity is beauty
tonych (OP)
Legendary
*
Offline Offline

Activity: 964
Merit: 1008


View Profile WWW
December 10, 2016, 11:37:30 PM
 #1616

Could we just ask big exchanges to claim and distribute their Byteball to their users ? Like Poloniex and others exchange did with Ardor distribution ?

Because really that would make everyone life easier and more people will be aware about Byteball.

That would be ideal, but it's still hard to convince them they should care.

Simplicity is beauty
Seccour
Legendary
*
Offline Offline

Activity: 1619
Merit: 1004


Bitcoiner, Crypto-anarchist and Cypherpunk.


View Profile
December 10, 2016, 11:45:36 PM
 #1617

Why would lowering the micropayment be riskier than with the current micropayments? (because they would be easily spotted?)

Because the attack would become cheaper, hence worthwhile.

mmmm, in my opinion the attack is already worthwhile, anyway such an attack won't succeed unless the attackee is not vigilant and doesn't double check their address (as the bot instructs them), so why not lower it if it permits to filter out exchanges addresses at the detection process (not requiring you to check suspect addresses)?

People do make mistakes, and having to be overly vigilant scares them off.  I'd rather have a more comfortable environment for the entire process.
The attacker's ROI depends on 3 factors:
- % of people who do not check that the address is theirs after receiving a second notification "Received your payment from ..." (the attacker's microtransaction is almost certainly later than the legitimate one)
- average balance of such users
- cost of attacking, which is the average amount of the microtransaction
By lowering the cost, we turn the ROI at some point from negative to positive.

I see your point. If you are comfortable with filtering out exchanges addresses after adding them and then investigating them, then there is no need to lower the micropayment. Yet, I still think lowering it would easily filter any exchange address out as the transaction won't be possible to begin with. (and if I were an attacker, paying (n times) 0.000x instead of 0.0000x wouldn't hurt my ROI that much Smiley).

I agree, but instead of manual filtering, maybe requiring signatures on an amount above X would be beneficial since it wouldn't be hurting anyone; those who are not good at technology usually own less Bitcoin. Plus, it would greatly reduce the effect of those who are putting in exchange/joint wallet addresses. That way, it would only exclude those who cheat the system.

Could we just ask big exchanges to claim and distribute their Byteball to their users ? Like Poloniex and others exchange did with Ardor distribution ?

Because really that would make everyone life easier and more people will be aware about Byteball.

I highly doubt all exchanges would agree to do that. Even the small exchanges have considerable amounts of BTC in their wallets.

We just need one big exchange such as Poloniex to do it and it will bring enough attention to Byteball. This + all the ICOs "whales" diluting each others byteball, we can have an equilibrium with our own funds as individuals.

Joint Force
Hero Member
*****
Offline Offline

Activity: 804
Merit: 500

DAO ↔ DApp


View Profile WWW
December 11, 2016, 12:22:34 AM
 #1618


What's the projected % of total byeball coins each person would receive for setting up a node?

valley365
Hero Member
*****
Offline Offline

Activity: 868
Merit: 1003


View Profile
December 11, 2016, 02:20:56 AM
 #1619


We just need one big exchange such as Poloniex to do it and it will bring enough attention to Byteball. This + all the ICOs "whales" diluting each others byteball, we can have an equilibrium with our own funds as individuals.

Exchanges have their own things to worry about. To do this kind of distribution is a not-so-small task for them, and what do they get from it? So I don't think they will care unless they get a fee out of it.
Seccour
Legendary
*
Offline Offline

Activity: 1619
Merit: 1004


Bitcoiner, Crypto-anarchist and Cypherpunk.


View Profile
December 11, 2016, 08:36:49 AM
 #1620


We just need one big exchange such as Poloniex to do it and it will bring enough attention to Byteball. This + all the ICOs "whales" diluting each others byteball, we can have an equilibrium with our own funds as individuals.

Exchanges have their own things to worry about. To do this kind of distribution is a not-so-small task for them, and what do they get from it? So I don't think they will care unless they get a fee out of it.

They have BTC, so they will get byteball. And if they accept it after the distribution they will win fees since people are going to sell and buy their byteball. It's a win-win for them to do it.

Pages: « 1 ... 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 [81] 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 ... 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!