Difference between revisions of "Distribution"

From Obyte Wiki
m (removed whitespace)
(added section: Sending rapid transactions)
Line 16: Line 16:
 
In order to '''do''' anything much with your Byteball wallet, you at least need enough for transaction fees to send [[token]]s. Sometimes it is tricky for a new person to get any bytes, athough enough to send transactions are not expensive. From the [[glossary]]:
 
In order to '''do''' anything much with your Byteball wallet, you at least need enough for transaction fees to send [[token]]s. Sometimes it is tricky for a new person to get any bytes, athough enough to send transactions are not expensive. From the [[glossary]]:
 
<blockquote>TRANSACTION FEE: The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Byteball database will cost 18,000 (white)bytes to send there. Currently a usual transaction fee is maybe 500 bytes, with a blackbytes fee being maybe 1000 bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.</blockquote>
 
<blockquote>TRANSACTION FEE: The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Byteball database will cost 18,000 (white)bytes to send there. Currently a usual transaction fee is maybe 500 bytes, with a blackbytes fee being maybe 1000 bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.</blockquote>
 +
 +
===Sending rapid transactions===
 +
If you are at a meet-up, with ten people around you all presenting their Receive QR codes, and you want to give each one their promised 100,000 bytes, you need to have prepared beforehand. Be aware how [[change address]]es work, and using the [[Send#Switch_to_multi-address|multi-address function]] send enough (10? 20?) payments of perhaps 5000 bytes to yourself first. Otherwise you might have to wait 10 minutes between each transaction, which would be a disaster at a meet-up promoting Byteball.
  
 
==How to get 10,000 to 100,000 bytes==
 
==How to get 10,000 to 100,000 bytes==

Revision as of 14:56, 22 March 2018

Introduction

We want Byteball wallets being used widely by as many people as possible. This comes from Metcalfe's law, namely that the effect of a telecommunications network is proportional to the square of the number of connected users of the system.[1]

Of course, the more popular Byteball is, the more people see or hear about it in videos, articles, video games <gulp> and general conversation, the more users there will be, and the more the $GBYTE value will tend to rise.

Marketing Byteball

This section is to be created another day.

Distributing wallets

Direct people to www.byteball.org to download a wallet.

Getting people to USE their wallet

This section is to be mainly created another day.

Transaction fees

In order to do anything much with your Byteball wallet, you at least need enough for transaction fees to send tokens. Sometimes it is tricky for a new person to get any bytes, athough enough to send transactions are not expensive. From the glossary:

TRANSACTION FEE: The fee you pay is identical to the size of the data you want stored. So a storage unit that takes up 18,000 bytes in the distributed Byteball database will cost 18,000 (white)bytes to send there. Currently a usual transaction fee is maybe 500 bytes, with a blackbytes fee being maybe 1000 bytes or so. If 1GB = $750, then 1MB = $0.75, and 1KB (1000 bytes) = $0.00075. So that's less than 1/10 cent US.

Sending rapid transactions

If you are at a meet-up, with ten people around you all presenting their Receive QR codes, and you want to give each one their promised 100,000 bytes, you need to have prepared beforehand. Be aware how change addresses work, and using the multi-address function send enough (10? 20?) payments of perhaps 5000 bytes to yourself first. Otherwise you might have to wait 10 minutes between each transaction, which would be a disaster at a meet-up promoting Byteball.

How to get 10,000 to 100,000 bytes

This is enough to send up to 200 Byteball transactions, but 100,000 bytes is less than 10 cents US!

The methods below will not scale to thousands of new users a day. But currently, Spring 2018, it is tricky for a new person without an existing Exchange account to obtain even a few cents' worth of bytes.

From a friend

This is the easiest way, whether the friend is present or remote. Includes local meet-ups for small groups.

  • In person: Someone with a Byteball wallet on their smartphone is right there with you. You download and install a wallet, click the Receive tab to display the QR code, and your friend instantly transfers the bytes to you.
  • Remote: Download/install the wallet. Click the Receive tab, copy your address, message it to the friend via email or some other app. Your friend simply sends the bytes to that address.
  • Textcoins: If immediate transfer of bytes to your wallet is not possible, at least the friend can send you a textcoin via email or other texting app. You can then import the bytes into your wallet when online again.

From a stranger on social media

These are just Byteball fans willing to respond to a dozen or so requests. For example, Slackjore tweeted:

I will send between 110,000 and 10,000 #Byteball bytes to the first 100 byte-poor people to reply with an address. Once per person please.[2]

To keep track of the 100, the first response received 110,000 bytes, the second 109,000 bytes, and so on. He sometimes checked the address given to make sure the person qualified as "byte-poor", but even if they were dishonest the amounts involved were so small that it didn't matter much.

If any Byteball fans are willing to do this sort of thing, contact @slackjore to get included below.

Twitter

  • @slackjore: Tweet @slackjore if you are byte-poor to get between 63,000 and 10,000 bytes (54 slots left out of the original 100).
  • Any other offers?

Facebook

  • Any offers?

Online from a regular merchant

This category is for Byteball fans who already have an online store with merchant software in place to process fiat payments by credit card, PayPal etc. They may or may not currently accept crypto payments. The idea is for the merchant to sell 100,000 bytes for $1 or £1 or €1 as a small sideline to his regular business, simply to help get Byteball into wider use. The bytes can be delivered to the buyer's Byteball address or sent as a textcoin, as appropriate.

Such stores will be gladly listed here:

  • (Example) Pete's T-Shirts: www.petes-tees.fake. 100KB for $1.00. Mohair T-shirts for men, women, children, and pets.
  • Any offers?

By mail from a Byteball fan

A Byteball fan makes a mailing address available to be posted here at least. Someone mails $1 or £1 or €1 CASH along with their Byteball address (such as JARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R). He sends the 100,000 bytes within 24 hours. $1 or £1 is not too much for the sender to risk, and the Byteball fan providing the service makes a few bucks in his spare time.

  • (Example) Mike Westin: 3016A Burlington Way, Los Angeles CA 90023 (fake address). $1 CASH for 100,000 bytes. Enclose your Byteball address (such as JARJFJ6SKDC2XGLX2XSNMIITAVRDEW2R).
  • Any offers?

From an online faucet

This could happen, and an automated system scales much better than a human one. One problem is to make it fraud-proof. 100,000 bytes isn't much, but if a scammer works out some way of draining the faucet rapidly, it's hard to keep it open for other people.

References