Im currently building a dApp where users will create content that then can be bet on by other users. The design opens up the problem of a user creating content,logging in with another wallet address, and betting on his own content, thus knowing the outcome. Is there any way I can get around this? I'm honestly stumped.
As accounts are pseudonymous, there's no way directly around this problem. Unfortunately I can't think of any alternative (better) way to accomplish this either.
Some ideas which will mostly fail:
Asking users to stake Ether to their votes. Doesn't change the problem much but might mitigate it a little bit - someone has to have multiple times the same stake (in different accounts) in order to get his candidate to vote.
Assigning voters some sort of unique ID or similar with which they have to vote. Won't really work as all information on blockchain is public and anyone can just claim somebody else's ID.
A reputation system of sorts. Doesn't really prevent anyone from having good reputation in multiple accounts.
I'd say you have to rethink your idea for a dApp as this model is not suitable for Ethereum.