Obyte: Totally new consensus algorithm + private untraceable payments

[kola-schaar]

Where can I find instructions how to participate in this airdrop? What does the change consist of compared to previously?

Our wiki is a good source of information: https://wiki.byteball.org/airdrop

..and you should not miss the OP:
https://bitcointalk.org/index.php?topic=1608859.0 .
There are also several tutorials:

http://bitviser.info/

http://dailybyteball.blogspot.de/2017/03/how-to-link-bitcoin-address-for.html
http://dailybyteball.blogspot.de/2017/03/how-to-sign-message-with-bitcoin.html
http://dailybyteball.blogspot.de/2017/03/how-to-sign-message-with-bitcoin_15.html

https://byteballblog.wordpress.com/how-to-get-free-byteballs
..and some videos on Youtube

Q2: maybe helpful => https://bitcointalk.org/index.php?topic=1608859.msg19463045#msg19463045

[dreamhouse]

Look here: https://wiki.byteball.org/asset

Waves has had quite a lot of token-spam: people create a token, send it to all addresses with a balance, create a hype, and profit on the decentralized exchange. I think that got less as the Waves-price went up, making it more expensive to spam the network.
In Byteball, trading them will be a bit more difficult, but sending them is much cheaper: less than a dollar is enough to send 2000 transactions. The Transition site has a convenient list of addresses.

Yes exactly, I saw a few wave-based tokens, some are for ICO but apparently nothing really new there. Byteball has many good features, just need more apps built on top of it.

[sailthor]

Hi,

I participated in my first round about 2 wks ago and never received any blackbytes. I received the bytes though. Is there anything I may have done wrong to not get any blackbytes? I have 3 bitcoin addresses linked and signed.

[tonych]

We are launching grants program to solicit work that improves the platform. 

See the full story https://medium.com/byteball/byteball-grants-program-906a71b93d3c

[onetwo12]

1GB=0.5BTC coming very soon!

let's wait for this.

[onetwo12]

Byteball Grants Program

Today we are launching Byteball Grants Program. We’ll pay for work that improves the ecosystem. We want the contributors to both come up with new ideas and realize them.
Similar programs have worked or are still working within other projects such as Dash and Ethereum and proved their success, e.g. Casper and MetaMask came out of Ethereum DEVgrants program.
The grants will be paid from our Community Fund which is funded by donations and undistributed blackbytes.
The process of awarding the grants will be as public and transparent as possible. Below are the rules, they might be amended in the future and evolve as we gain experience. If you have any ideas how to make the platform better and ready to do it yourself or with your team, feel free to apply.
Byteball Grants
Grants are paid for work that contributes to Byteball ecosystem. The work is not limited to development only, it can be any other work (such as marketing, promotion) that potentially adds value to Byteball platform as a whole.
Grants are paid out of the Community Fund.
The general procedure is as follows:
Applicant(s) come up with an idea that can be realized by the applicant(s) and would potentially add value to the platform
Applicant(s) draft a pre-proposal and offer it for public discussion. The pre-proposal includes the what and why of the work as well as milestones and requested funding.
After public discussion and based on community feedback, the applicant(s) optionally amend the pre-proposal and submit a final proposal.
The proposal is voted by the community fund trustees and approved based on 3-of-4 majority, or rejected.
The applicant(s) publish regular updates about their ongoing work and the funds are released based on achieved milestones.
Proposals and pre-proposals
Proposals and pre-proposals have the same content requirements, the difference being only that pre-proposals are submitted to the community for public discussion and can be amended many times to incorporate feedback from the community, while proposals are final formal documents that necessarily trigger trustee vote.
It’s up to the applicant(s) to decide when their pre-proposal has matured to be submitted as a finished proposal but at least a week of public discussion is recommended.
Applicant(s) can withdraw their pre-proposal at any time for any reason.
Proposals and pre-proposals should be published as an online document (google doc, etc) and a link to the document, as well as its summary, should be published in Slack channel #grants. It is recommended to discuss the pre-proposal in a Slack thread started by the pre-proposal.
Content of (pre)proposal
Each (pre)proposal description should include:
What will be done, what are the deliverables
What problem it solves
Timeline and milestones: when and what parts of the project will be ready. Small projects include only one (final) milestone
Requested payment schedule in GB, GBB, and fiat. It must be linked to milestones and should specify how much should be paid against completion of every milestone, plus optionally one pre-payment that should be released immediately after the proposal is approved and before its implementation is started. The schedule can contain payments in fiat e.g. if the applicant’s costs are in fiat, it will be converted to GB or GBB at the time of payment at then-current rates.
Total budget
Team member(s) and their roles in the project and backgrounds
Depending on the nature of the proposal, before a pre-proposal is submitted for the first time, a research should be done to show that what is proposed is doable.
Discussion of pre-proposal
Any community member can comment on the proposal, say how would he/she vote, suggest improvements and amendments.
Final proposal and vote
After discussion the applicants optionally amend their proposal and submit it for vote to the trustees. Trustees vote is based on the merits of the proposal as well as the available funds. Trustees take into account the community feedback during discussion.
Resubmission
A rejected proposal can be submitted again after making amendments and going through a new public discussion.
Reporting and payment
After a proposal is approved, the applicant(s) start working on it. When milestones are achieved, the applicant(s) publicly announce the achievement of the milestone in #grants and request the trustees to release the payment bound to this milestone. Both community members and the trustees evaluate the results of the work and the trustees release the payment within the following 7 days if they find that the milestone was actually achieved.
Acceptance guidelines
For-profit projects are generally not accepted but can be considered if they are long term and significantly improve the ecosystem
Requesting a pre-payment is discouraged unless it is dictated by the nature of the project
Anonymous team members are OK but requesting a prepayment is even more discouraged in this case
Do not duplicate the work of other published (pre)proposals
If development, the work must be open source and under any free license during the entire lifetime of the project
Creative work, documentation, etc should be released under any free license (such as Creative Commons)
Most projects should last less than 3 months

that's really great!

[NUFCrichard]

Hi,

I participated in my first round about 2 wks ago and never received any blackbytes. I received the bytes though. Is there anything I may have done wrong to not get any blackbytes? I have 3 bitcoin addresses linked and signed.

As I understand it, you only get blackbytes in an airdrop when you already have byteballs in your wallet.
You (and I) didn't have any byteballs, so we only got byteballs, not blackbytes.

If you held, you should get Blackbytes next time. 

[LoyceV]

I participated in my first round about 2 wks ago and never received any blackbytes. I received the bytes though. Is there anything I may have done wrong to not get any blackbytes? I have 3 bitcoin addresses linked and signed.

Sometimes sending blackbytes seems to fail, you can ask tonych to check: send him a kind message with your Byteball address so he can resend them.

NUFCrichard above is wrong, he clearly didn't read the OP:

BTC to blackbytes: 1 BTC of proven balance gives you 2.1111 * 62.5 million blackbytes

[davidoski]

Much vaunted Eth is having a congestion problem causing overall cryptomarket into a downside push. I wonder how would Byteball deal with a similar load of transactions. Would it handle it better?

https://news.bitcoin.com/status-ico-generates-over-60-million-but-fails-to-deliver-meanwhile-ethereum-flounders/

As I understand, in theory, as Byteball i not using BlockChain but a Directed Acyclic Graph (DAG) a.k.a "Tangle", it is not concerned by overload of transactions. Is it the otherway around, the more transactions, the quicker they are confirmed.

https://explorer.byteball.org/#W/xyYlbV7wP5nkZ46s73dWi+EBjFgpzNkbCkld+jI0c= The Graph become larger when the number of transaction increase.

The bottleneck in this setup are full nodes (and to some extent light nodes) and synchronization. Imagine 20.000 tps. With such huge load full nodes would not keep up with new transactions coming and they would be in constant synchronizing state. The same applies to witnesses, oracles etc. 

[CorePrime95]

We are launching grants program to solicit work that improves the platform. 

See the full story https://medium.com/byteball/byteball-grants-program-906a71b93d3c

Great news! The future is bright for Byteball  

[ByteFan]

Much vaunted Eth is having a congestion problem causing overall cryptomarket into a downside push. I wonder how would Byteball deal with a similar load of transactions. Would it handle it better?

https://news.bitcoin.com/status-ico-generates-over-60-million-but-fails-to-deliver-meanwhile-ethereum-flounders/

As I understand, in theory, as Byteball i not using BlockChain but a Directed Acyclic Graph (DAG) a.k.a "Tangle", it is not concerned by overload of transactions. Is it the otherway around, the more transactions, the quicker they are confirmed.

https://explorer.byteball.org/#W/xyYlbV7wP5nkZ46s73dWi+EBjFgpzNkbCkld+jI0c= The Graph become larger when the number of transaction increase.

The bottleneck in this setup are full nodes (and to some extent light nodes) and synchronization. Imagine 20.000 tps. With such huge load full nodes would not keep up with new transactions coming and they would be in constant synchronizing state. The same applies to witnesses, oracles etc.  

Right. The transactions have to spread around all the network. This takes time. No decentralyzed network will never reach 20.000 tps DAG or not DAG.

[sheld0n]

Hi,

I participated in my first round about 2 wks ago and never received any blackbytes. I received the bytes though. Is there anything I may have done wrong to not get any blackbytes? I have 3 bitcoin addresses linked and signed.

Yes, you probably have not stored your bytes on the address given in the chat bot overview of your addresses. In the end of the chat bot message there is a address where to send the bytes.

Don't worry, it is one of your addresses but the bytes have to be stored on this special address in order to receive blackbytes.

[hey_monkey]

Much vaunted Eth is having a congestion problem causing overall cryptomarket into a downside push. I wonder how would Byteball deal with a similar load of transactions. Would it handle it better?

https://news.bitcoin.com/status-ico-generates-over-60-million-but-fails-to-deliver-meanwhile-ethereum-flounders/

As I understand, in theory, as Byteball i not using BlockChain but a Directed Acyclic Graph (DAG) a.k.a "Tangle", it is not concerned by overload of transactions. Is it the otherway around, the more transactions, the quicker they are confirmed.

https://explorer.byteball.org/#W/xyYlbV7wP5nkZ46s73dWi+EBjFgpzNkbCkld+jI0c= The Graph become larger when the number of transaction increase.

The bottleneck in this setup are full nodes (and to some extent light nodes) and synchronization. Imagine 20.000 tps. With such huge load full nodes would not keep up with new transactions coming and they would be in constant synchronizing state. The same applies to witnesses, oracles etc. 

In this case (20000tps) we will have a huge bunch of full nodes and witnesses, each will not need to be aware of all the transaction immediately. isn't it?

[galaxiekyl]

sell gbb: 28GBB>1.4GB

pm me.

[jaberwock]

sell gbb: 28GBB>1.4GB

pm me.

There is a topic for byteball trade sir, it doesn't belongs here

https://bitcointalk.org/index.php?topic=1728405.0

[testerx]

I think if we get people to think of the price in terms of megabytes instead of gigabytes it'll help long term price growth.  I think people are seeing $700+ and being scared off because they think they have to buy an entire gigabyte.

[davidoski]

Much vaunted Eth is having a congestion problem causing overall cryptomarket into a downside push. I wonder how would Byteball deal with a similar load of transactions. Would it handle it better?

https://news.bitcoin.com/status-ico-generates-over-60-million-but-fails-to-deliver-meanwhile-ethereum-flounders/

As I understand, in theory, as Byteball i not using BlockChain but a Directed Acyclic Graph (DAG) a.k.a "Tangle", it is not concerned by overload of transactions. Is it the otherway around, the more transactions, the quicker they are confirmed.

https://explorer.byteball.org/#W/xyYlbV7wP5nkZ46s73dWi+EBjFgpzNkbCkld+jI0c= The Graph become larger when the number of transaction increase.

The bottleneck in this setup are full nodes (and to some extent light nodes) and synchronization. Imagine 20.000 tps. With such huge load full nodes would not keep up with new transactions coming and they would be in constant synchronizing state. The same applies to witnesses, oracles etc.  

In this case (20000tps) we will have a huge bunch of full nodes and witnesses, each will not need to be aware of all the transaction immediately. isn't it?

Unfortunately it is. Every full node stores a full DAG database which contains the history of all transactions ever happened. There's no sharding/pruning as of now.

[qero]

What control airdrop funds in this wallet (wallet with the last 730k Gbyte)?
https://explorer.byteball.org/#MZ4GUQC7WUKZKKLGAS3H3FSDKLHI7HFO
Are these funds in hands of dev or it's smart contract that generate airdrops automatically?
Thanks.

[ByteFan]

What control airdrop funds in this wallet (wallet with the last 730k Gbyte)?
https://explorer.byteball.org/#MZ4GUQC7WUKZKKLGAS3H3FSDKLHI7HFO
Are these funds in hands of dev or it's smart contract that generate airdrops automatically?
Thanks.

Yes it is in dev hand. See https://byteball.fr/Top100ByteballRichest.php

Distribution is manualy triggered by Tonych

[CarlOrff]

In the wiki (https://wiki.byteball.org/airdrop), you wrote :

The snapshot for the 7th round will be taken at the full moon of July, on July 9, 2017 at 04:07 UTC. If you linked your BTC address(es) correctly, proving your balance at that moment in time, you will get delivered to your full or light wallet all of these that apply:
    BTC to bytes: For every 1 BTC, 62.5 MB [0.0625 GB or 62,500,000 (white)bytes]
    BTC to blackbytes: For every 1 BTC, 2.1111 x 62.5 million blackbytes (money supply of blackbytes is 2.1111 times as much as that of bytes)
    Bytes to bytes: For every 10 (white)bytes on any Byteball address, 2 new (white)bytes
    Bytes to blackbytes: For every 10 (white)bytes on a linked Byteball address: 4.2222 new blackbytes

In the last sentence : "Bytes to blackbytes: For every 10 (white)bytes on a linked Byteball address: 4.2222 new blackbytes",
What do you mean by a linked Byteball address ? Linked to what ?
I understand what is the BTC linked address, bur the linked Bytewall address, not sure...
In my case, i have many BTC addresses linked to my Byteball address, but I have only one ByteBall address, but not linked to anything (except the BTC address, of course).