The LUV and HBIT tokens have simple goals and try to keep things simple.
- [LUV](https://peakd.com/luv/@luvshares/about) - share LUV on the Hive chain with others and expect nothing in return
- [HBIT](https://peakd.com/hive/@hivebits/about) - rewards your effort and ensures that every token is backed by proof that someone exerted some effort at some time.

In both cases, the desire is to keep barriers-to-entry low and barriers-to-use low. With LUV, only 10 are needed to give freely to others. With HBIT, a Hive newbie could literally mine HBIT as his or her first Hive action. Simple is good.

The simplicity and low barriers require a degree of trust and responsibility. Not all people can be trusted, or they are irresponsible, or they are selfish. Probably, we all have degrees of each of these vices. Yet, some people are just simply bad actors. And, their actions can hurt, [as described in this post](https://peakd.com/hive-103408/@kvinna/sei-bitte-achtsam-auf-der-blockchain-please-be-mindful-on-the-blockchain) by @kvinna.

Thankfully, on an open blockchain like Hive, *everything is open and transparent for all to see!* As the saying goes: 

>"Sunlight is the best disinfectant." [Source](https://quoteinvestigator.com/2020/09/22/sunlight/).

#### LUV is calling for "Inspectors" to help keep an eye out for bad actors.

<center>
https://files.peakd.com/file/peakd-hive/luvshares/EoKCZM15BNhQVScb5yVwzSgEs7D9ERwqn5EryZ8bopY8Jsr4S9akSSChjdMPwxfrpgB.gif
</center>

**What are inspectors?**
Inspectors are people who keep an eye out for abuse and misuse of the LUV or Hivebits (HBIT) token. The idea and name came from @thatgermandude (see below). Inspectors could probably keep a watch out for abuse of other comment/tip/engagement tokens as well, since many of these bad actors seem to wrangle in these tokens also. It's nothing official, it's just people keeping watch for misuse.

**What is misuse?**

LUV misuse - The intent is to share love with *others* and expect nothing in return. The intent is *not* to farm-mine the LUV token for one's self.

HBIT misuse - The intent is to reward one's own effort, one HBIT per *person* per day. The intent is *not* to farm-mine HBIT beyond that.

**How do Inspectors inspect?**
Inspectors use their tools.
1. The most basic way for anyone to help is to just **keep an eye out**. Abuse usually pops up in the comments of posts. For instance, chains of comment/tip/engagement tokens send back-and-forth to/from the same users is a red flag.
2. Look at the Hive-Engine block explorers. [HE Explorer](https://he.dtools.dev/@luvshares?symbol=LUV) and [hive-engine.rocks](https://hive-engine.rocks/transactions?symbol=luv) are great. Entering usernames and/or token names can be enlightening. All actions from **all time** are there.
3. Look at Hive blockchain explorers. [Hiveblocks](https://hiveblocks.com/@luvshares) and [hive.ausbit.dev](https://hive.ausbit.dev/@luvshares) are great. Changing to a Hive user's username shows their **entire history**. For instance, by going to a user's first/oldest page (the largest page number at the bottom), you can see when the user began. Then, every single action could be traced from there. 
4. **Watch Discord**. The LUV server on Discord is at https://discord.gg/K5GvNhcPqR Two valuable tools there are the luv-log and hbit-log channels. They show all of the commands LUV and HBIT receive. Whereas the block explorers are great tools for *all time* history, Discord and the logs are great tools for **real time**...when a bad actor starts acting badly, there it is on display! 
5. **Watch the markets**. This requires a little experience with order books and depth charts, but this is how a recent oddity was first discovered. LUV markets: [H-E LUV](https://hive-engine.com/trade/LUV) | [Tribal LUV](https://tribaldex.com/trade/LUV) | [LeoDex LUV](https://leodex.io/market/LUV); or for Hivebits: [H-E HBIT](https://hive-engine.com/trade/HBIT) | [Tribal HBIT](https://tribaldex.com/trade/HBIT) | [LeoDex HBIT](https://leodex.io/market/HBIT).
6. Check [Hive-Engine Classic](https://cfoxon.github.io/). [Originally used but now offline: ~~https://jjb777.github.io/hive-engine-classic/~~.] This tool not only shows H-E transactions, but also *shows the usernames* behind those transactions. Remember, *everything* on the chain is open and transparent. The [HBIT](https://cfoxon.github.io/?p=market&t=HBIT) page was used to uncover the bad actors recently (actually, it was *one person* with several alt usernames). 
7. Contact @crrdlx either on chain or on [Discord](https://discord.gg/K5GvNhcPqR). On chain you could publicly use comments, or you could use the private "chat" feature PeakD has handy. Discord is likely the fastest.

Case study: 

@thatgermandude recently noticed oddities in the HBIT order book and notified me. When a bad actor is suspected, checking his or her **recent** activities can reveal collusion with other bad actors. These "others" often turn out to be the same person hiding behind alt usernames and just *posing* as others. Also, checking **early** actions in a user's history can reveal who this user is in league with. Oftentimes, the fake username is supported by a "larger" user early on...maybe by receiving HP or Hive or HBD, or by getting upvotes or comments. So, I dug around using the tools above and the bad actor and alt-usernames were revealed. Similar to an FBI wall-chart with photos, clues, evidence, times and dates, all linked with red yarn, dots begin to connect and things tend to become clear. The bad actor and all of his many usernames were blocked.

>Using these tools is like opening the window and letting the sunlight shine in to disinfect.

**What happens if a user is suspected of bad action?**
1. Normally, that user will be contacted. This contact will be to educate and inform. The intent here is to let the user know that their actions are seen, but *not* to finger-point, shame, or embarrass. 
2. After notification, if the bad actions stop, then everything is just fine.
3. If things continue in a bad way, blocking will likely follow.

Note, if the abuse is egregious and obvious, I'll skip the notification and just block.

**What does being blocked mean?**
For LUV, this means they cannot give or receive the token. This means for Hivebits that they cannot mine HBIT or receive it if someone mined it in a reply to them. 

Any LUV or HBIT already owned (or pilfered) can still be traded on the Hive-Engine exchange...any tokens owned by a user's private keys, are controlled by those keys and user. Blocked users could also still be given LUV or HBIT *wallet-to-wallet* (just like any other H-E token). However, *they will be cut off from the LUVbot and HBITbot going forward*.

**How can I be an inspector?**

1. In a way, *you already are an inspector*. Anyone can keep an eye out. It's the adage, "See something, say something." Just helping out helps.
2. Give me, @crrdlx, a heads up. I will say this: my default is to lean toward accepting people's actions in the best possible way and being forgiving...even if that means I get burnt sometimes.
3. Comment or reply if something seems suspicious. It's a good idea to refer users to the "About" pages: [About LUV](https://peakd.com/@luvshares/about) | [About HBIT](https://peakd.com/hive/@hivebits/about)
4. Join the LUV (and HBIT) Discord and reach out to me there. (I'm crrdlx#2692 on Discord.) 

Thank you for helping. :)

Written by @crrdlx


----

> - Check your wallet or trade LUV at: [Hive-Engine](https://hive-engine.com/trade/LUV) or [TribalDEX](https://tribaldex.com/trade/LUV) or [LeoDEX](https://leodex.io/market/LUV).
>- Visit the LUVstore: [LUVstore](https://crrdlx.websavvy.work/luvstore/)
>- LUVshares Discord: [https://discord.gg/K5GvNhcPqR](https://discord.gg/K5GvNhcPqR)
>- LUVshares Telegram: [https://t.me/luvshares](https://t.me/luvshares)
>- LUVshares creator: [@crrdlx](@crrdlx)

<center>
<a href='https://peakd.com/@luvshares' target='_blank'><img src='https://files.peakd.com/file/peakd-hive/luvshares/M0PK3is2-LUVlogo-125.gif'/></a>
<sub>@LUVshares - Share the LUV.</sub></center>
</center>
<center>
[<><](https://ichthys.netlify.app/)
</center>