samporter1984/aletheo

A marketing tool.

Aletheo(LET)

From Greek it's the Bringer of truth from God, or simply God of Truth. Most of the development is now in private repo/background for a bit while

• https://t.me/aletheo
• https://t.me/aletheonews
• https://discord.gg/rDd5sAHQ4S

To properly run tests make sure your init code hash for uniswap is valid.

git clone https://github.com/SamPorter1984/Aletheo && cd Aletheo && npm run test

Because of EIP-3561 specifically designed for Aletheo, refactoring and optimization is not critical as of now, so the recent version of Aletheo smart contracts does not look as nice, as it was before.

You can find EIP-3561 tests in this repo.

Next version of whitepaper soon, latest is 0.6 and has a couple of errors in design.

The browser extension for anonymous imageboards was removed from here and will have a separate repo soon.

Tests for EIP-6228 will be moved to a new repo.

aletheo's Issues

Aletheo - whitepaper translations

Translations of this Aletheo Whitepaper 0.5.pdf in this folder: https://github.com/SamPorter1984/Aletheo/blob/main/papers/
The document is 10 pages long, and as of now still a draft, but you can disregard that, you can just translate 0.5. $300 in Ether or LET for a translation(assuming that Founding Event will gain Ether and LET token will have value, probably not, because I can't project or imply returns and in my eyes LET token is always $0, and if it somehow isn't, it will dump to $0, and Founding Event will gather exactly 0 Ether)

Translations of the whitepaper can be paid in Ether as Founding Event progresses, or in LET tokens after Founding Event concludes, in case if the Event won't gain enough Ether.

We need the paper to be translated to:

1.Chinese

2.Japanese

3.German - telegram: Marlen F. already applied

4.French -@hugobsky has already applied. @FranckRO is pending after @hugobsky

5.Portuguese - @nicemarcela has already applied. @sandro1305 is pending after @nicemarcela

6.Italian - @roxennnn already applied

7.Russian - @moshenskyDV already finished

8.Korean - @visavis2k already applied. If he does not deliver, then @KurosenAo will be the next applicant

9.Spanish - @zant has already finished

10.Indonesian - @ginzbitcoin already applied. @KurosenAo is pending after him, if he won't deliver

11.Dutch - @simluyt has already applied

12.Arabic - @samhar1995 already applied for better quality. Previous applicant' (telegram: @MRM_XO) translation was found to be of extraordinary low quality, so we will pay him, but much less.

13.Swedish - @samhar1995 already applied

14.Polish - @mpawlowski85 already applied. @drumlive is pending, in case if @mpawlowski85 won't deliver

15.Thai - @ozairm

16.Norwegian - @mrkurger already applied

17.Danish

18.Finnish - @jlindlof already applied

19.Greek - Telegram @dinowy already applied

20.Turkish - @Mlhozgr already applied and finished

21.Slovak - @goldenqo already applied and finished

22.Hindi - @iamank1t already applied. We have all 3 Indian community managers, @amalnathsathyan, @iamank1t and @6ug2.

23.Serbian - @Divljo31 already applied and finished

24.Hebrew

25.Khmer

26.Malaysian

Also, if a community of a particular language says that the translation of the whitepaper is still very bad, mods will have to translate it, but they won't receive $300(actually $0 on top of $0) on top of their LET tokens salary.

Aletheo - $0(zero) for severe/critical vulnerability. Bug bounty hunters/auditors are required

Why so low? Can it go any lower? Well it is supposed to be $1000000, but since I can't project or imply any returns, in my eyes LET token is always $0, and if it somehow isn't - then it will dump to $0. That if, you are from US.
$1000000? Why so high? Is this a scam? We believe that a company usually can't have a bug bounty this high since it's a group of people and they can't have confidence in the code, especially if it's in active on-going development. On the other hand, smallest teams and solo developers can have confidence. Let's see if I ever have to pay this

Bug bounty for live mainnet contracts on Ethereum Blockchain. More contracts will be added to this list, as soon as we find it suitable and ready for Audit/Bug Bounty program.

LET token trust minimized proxy: https://etherscan.io/address/0xed7c1848fa90e6cda4faac7f61752857461af284#code

LET token current implementation which can't be upgraded until certain block: https://etherscan.io/address/0xb321c6207a215360ac376a816c44b77347d9dc53#code

Founding Event: https://etherscan.io/address/0x31a188024fcd6e462abf157f879fb7da37d6ab2f#code

Staking trust minimized proxy: https://etherscan.io/address/0x93bf14c7cf7250b09d78d4eadfd79fca01bad9f8#code

Staking current implementation which can't be upgraded until certain block: https://etherscan.io/address/0x2f31e7527e69d235bf77b514dd5230941e6a9855#code

Treasury trust minimized proxy: https://etherscan.io/address/0x05658a207a56aa2d6b2821883d373f59ac6a2fc3#code (overflow bug was already noticed, is being fixed by plugging in logic locking it in proxy and this logic must have additional limits)

Treasury current implementation which can't be upgraded until certain block:

Oracle registry trust minimized proxy: https://etherscan.io/address/0x742133180738679782538c9e66a03d0c0270ace8#code

Oracle registry current implementation which can't be upgraded until certain block:

Job market trust minimized proxy:

Job market current implementation which can't be upgraded until certain block:

Assume that deployer is also an attacker(deploying first malicious logic for job market and oracle registry does not count though, this is covered by game theory, assuming that founding event will last much longer than the limit also does not count as a bug, since it's intended behavior, and proxy locks are going to be prolonged accordingly). Anything basically, what if contracts were initialized in a wrong way, typos in hardcoded addresses, etc

severe/critical vulnerability allows attacker to steal at least an equivalent of $1000 or more in LET tokens or LET-ETH LP tokens or Ether in a span of 24 hours or less from an address that does not belong to the attacker(or just lose/terminate an equivalent of $1000 or more in a span of 24 hours or less from an address that does not belong to the attacker) strictly by interacting with aforementioned contracts as an attacker, so without social engineering without directing users to a malicious dApp interface, without counting for Ethereum 51% attacks, etc - $1000000 in LET tokens(Assuming that LET will have value, probably not)

moderate vulnerability allows attacker to steal less than an equivalent of $1000 in LET tokens or LET-ETH LP tokens or Ether in a span of 24 hours or less from an address that does not belong to the attacker(or just lose/terminate an equivalent of less than $1000 in a span of 24 hours or less from an address that does not belong to the attacker) or moderate vulnerability does not allow attacker to steal money but rather somehow interrupt intended behavior of aforementioned contracts, for example not to lose participants' money but drop their rewards to 0 or something - $100000(Assuming that LET will have value, probably not)

low vulnerability is anything that does not fit into severe/critical or moderate vulnerability definition in the issue - $10000(Assuming that LET will have value, probably not)

The bounty for low and moderate vulnerabilities could decrease though, if I will get spammed with useless submissions. The bounty for severe/critical vulnerabilities will never decrease even if I get spammed with useless submissions.

For transparency all vulnerabilities can be and should be submitted publicly(anywhere where I can't possibly delete it, and then you can drop a link with explanation of vulnerability here to this bounty), even if it's a critical vulnerability which can be exploited by anybody. Everybody should know that it was you who discovered something to minimize trust for payment. But of course, if you feel like it's best to notify in pm, you can reach out on Twitter https://twitter.com/SamPorter1984 or Telegram https://t.me/SamPorter1984

The bounty will be paid overtime out of allocation of the developer who wrote these contracts(in this case me). 75% of maximum possible emission my allocation has will always go to reward bug bounty, if there is any reward to pay. The bounty or a part of the bounty will be paid monthly according to monthly index of LET to USD. If the project fails to gain sufficient enough value for me to ever pay you the bounty, can only pay as much as possible and say thanks.

Submitting the bug report for any contracts or programs not mentioned here won't get you money, we know that our drafts are probably vulnerable. Commented out code does not count either. If I discover a vulnerability myself first - I will publicly announce this, and after that I am not obliged to pay you for rediscovering it, that's another reason why you may want to first publicly announce discovered vulnerability instead of dropping it to me in pm, to again, remove trust, because I could not find a way yet for me to prove the integrity of my intention to pay. You have to have low enough IQ to understand what the project is about and see what it means to put my reputation at stake even if I am anonymous and work with trust minimized proxies.

If you publicly report something, but I won't pay you - I destroy my reputation and the reputation of this project, and it's impossible for me to de-risk it like a typical ICO, I can claim all my tokens only in 34 years or so from inception(depends on block time)

The history of edits of this Github issue can be easily tracked as long as Github works correctly. If I remove the issue from Github - I also damage the reputation of the project.

There is no way for me to remove your comment from your Gitcoin page as long as Gitcoin works correctly. If I cancel the bounty - I also damage the reputation of the project.