* Bot is written in a C/C++ mix. (slowly merging into a C++ OOP design)
    * Code base of eggdrop 1.6.13 (The code has evolved so much in 4 years that it can't even be compared to eggdrop anymore).
    * TCL not required/supported.
    * No module support.
    * Initially influenced by the ghost botpack.
    * The source code is private; binaries are distributed.
    * There is only 1 version of a binary for each Operating System. Ie, hub and leaf binaries are the same.
    * Leaf bots act like dummie drones and save no botnet settings or files locally.
    * Binaries store information about bots internally; no config files used.
    * A botnet can be easily updated with new binaries from the hub. (see Updating)
    * Customizable dcc cmd prefix; ie !cmd %cmd *cmd.
    * Userfile contains channels, settings as well.
    * IPv6 support for irc/botnet.
    * Asynchronous Dns 

Encryption ¶

    * All botnet traffic/files are encrypted with AES-256+base64
    * Binaries store an assortment of MD5 checksums internally and verify them upon starting.
    * Binaries store data about bots internally with AES-256 encryption.
    * Botnet keys are randomly regenerated. 

DCC ¶

    * Secure login using AuthSystem.
    * Separation of cmds on hub and leaf bots.
    * Remote control of bots from hubs.
    * Users cannot access/view users of higher level. 

IRC ¶

    * Hubs do not connect to irc.
    * Autoaway at random intervals.
    * Client cloaking (CTCPs / version).
    * Mass op/deop protections.
    * Manual op protections.
    * Op cookies using custom hash/encryption scheme to protect from network stream hijack.
    * +take channel flag to quickly op botnet and mass deop channel.
    * No user exemptions or flags; No client is trusted without passwords.
    * +bitch channel flag uses multiple methods of protection.
    * Pre-defined list of kick reasons.
    * Auto limiter using algorythm to only set limit when needed.
    * Auto voicer to +v all clients, along with options to decide who gets voiced.
    * CIDR ban support
    * Bots prefer requesting op from bots on same server, or from list of bots sorted by hops.
    * Bots regain nick. 

Users ¶

    * CIDR hostmask support.
    * Multiple levels of control through flags.
    * "Perm" owners are statically defined in the binaries.
    * Sensitve control is through userflag +a (admin) (shell access, bot configuration, etc)
    * Botnet control is through userflag +n (owner)
    * User control is through userflag +m (master)
    * Channel control is through userflag +o (op) 

Leaf Bots ¶

    * Botnet list not visible.
    * Hubs not visible.
    * Hostmask not visible in whois.
    * Only bots with +c flag will accept /dcc chat or /ctcp CHAT.
    * No static telnet access.
    * Ports opened for /ctcp CHAT are automatically closed after a minute.
    * Cloaked respones for /dcc chat and /ctcp CHAT.
    * Do not save userfile (or channels), or any settings in files.
    * Bot data (bot.conf) stored internally in binary.
    * One binary may contain multiple bots..
    * One binary may spawn multiple bots..
    * Each bot gets its own process. (Not emech style or threaded) 

Botnet ¶

    * All user/channel settings are shared automatically.
    * Users need userflag +j to access leaf bots.
    * Users need userflag +i to access hub bots through telnet or .relay. 

Removed eggdrop features ¶

    * Modules
    * TCL
    * File area (filesys.mod)
    * Greet
    * userflag +f (friend)
    * userflag +t (botmaster)
    * Misc channel flags.
    * Blowfish
    * Assoc.mod
    * Seen.mod