These examples are perfect! Comma separated @ list, with the number of sponsees matching the amount of HIVE, or separate transactions with 1 HIVE sent for each member are both perfect. Model your transactions after these and you will be fine!
Please do not sponsor yourself. (Self-sponsoring is not recognized at all. You will get the normal 1 for each HIVE that you send, but the unit normally assigned to the person you sponsor will be assigned to somebody else.)
If you have a program sending the transactions, longer lists are fine. We have had transactions as large as 75 HIVE (with 75 different names) processed without any issues because all of the names were spelled correctly and the transaction followed our syntax perfectly.
Use whole numbers. Every transaction received is rounded down to a whole number, and you will not receive a refund of your excess amount. Even 1.999 would be treated as 1, and you and your sponsee will each receive only 1 unit added to your subscription level.
@sponsor:@sponsee, or sponsor:sponsee
Look at this transaction from @mastergerund, with memo that reads
blockchaininfo:rambutan.art. This results in 3 subscription units each for @blockchaininfo and
@rambutan.art, even though the transaction came from
@mastergerund. We currently have a few members that use this format regularly, and it works flawlessly as long as the syntax is followed. When there are spaces between the names and the
: symbol, it results in error.
You could also use this to submit enrollment transactions through @blocktrades or other exchanges. If you withdraw to
@steembasicincome with your transaction memo in this format, you can still receive credit for sponsoring (or sponsor people anonymously by having neither name be from you!)
The official currency for enrollment is HIVE. If we choose to accept HBD without refunding it, you do not receive extra value for it.
Enrollments are processed automatically every 144 minutes. Confirmation transactions are only sent for initial enrollment.
Most questions are addressed in our FAQ. If you still have questions, ask in the comments section or join us in our discord channel.