# Farming cred attacks/abuse

**URL:** <https://discourse.sourcecred.io/t/farming-cred-attacks-abuse/133>\
**Category:** Research\
**Created:** [July 27, 2019, 12:31pm UTC](https://discourse.sourcecred.io/t/farming-cred-attacks-abuse/133 "2019-07-27T12:31:30Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![decentralion](https://yyz2.discourse-cdn.com/flex032/user_avatar/discourse.sourcecred.io/decentralion/32/7_2.png) [@decentralion](https://discourse.sourcecred.io/u/decentralion)\
**Post date:** [July 31, 2019, 4:40pm UTC](https://discourse.sourcecred.io/t/farming-cred-attacks-abuse/133/6 "2019-07-31T16:40:57Z")

</div>

> [@s\_ben](#):
>
> So, with only a high-level understanding of the algorithm, I was under the (mistaken) assumption that cred only flowed to a contribution only if another contributor with cred interacted with it in some way. E.g. if someone posted a bikeshedding comment, and nobody interacted with it, it would get 0 cred.

“legacy” cred kind of worked this way; something that had no “incoming” edges from elsewhere in the project would tend not to have any cred, due to the absence of a seed vector. Now, because of the seed vector, everything in the repo “owns” some cred. Doing it this way made it a lot easier to reason about time-weighted cred (things “own” less and less cred when they are old), but I still think of it as a prototype, and expect we will develop a more sophisticated and robust algorithm in the future.

---

_[View the full topic](https://discourse.sourcecred.io/t/farming-cred-attacks-abuse/133)._
