web3j VS smart-contract-best-practices

Web3j: Lightweight Java and Android library for integration with Ethereum clients. https://www.web3labs.com/web3j-sdk

In the meantime, one thing that might be helpful for Android developers is updating the document and/or providing the workaround. If an Android developer follows the documentation, an app won't work. A note along the lines of "web3j for Android is down until further notice", "join the discord for the android workaround", ... might be helpful. There have been some hints (eg 1, 2) about workarounds setup and use, but as far as we can tell, web3j for android is currently broken. It appears that there might be a workaround for most, basic Android web3j functionality, even with v4.8.8-android. We'll try the discord.

Just to add: there is also web3j (https://github.com/web3j/web3j) for the Java people. You can use Maven/Gradle and it generates stubs (classes) which use can use to call the Smart Contracts on any EVM chain. And it is type-safe (as corresponding Java types are used for the Solidity types).

I'm trying to build a mobile app on a blockchain and unsure if a library like web3j would work with all blockchains that use JSON RPC

Congrats. As a java programmer you might find web3j useful: https://github.com/web3j/web3j

There really wasn’t as of about 2 years ago at least. I worked on a Clojure backend that integrated with Ethereum and went with Java interior using https://github.com/web3j/web3j which wasn’t too painful.

Hey, I develop a crypto trading app for Android and currently started with the implementation of an Ethereum wallet using web3j. If your are interested in contribution just contact me.

Try https://github.com/web3j/web3j

Then i delved into best practises (https://consensys.github.io/smart-contract-best-practices/) and patterns (https://fravoll.github.io/solidity-patterns/) to improve.

Search for solidity exploits on Google, useful one: https://consensys.github.io/smart-contract-best-practices/ there are a lot of possible exploits so deploying one by yourself without audits is a no-go imo

Consensys' Smart Contract Best Practices is a good start for security related stuff (super important because you'll be dealing with people's money in smart contracts) https://consensys.github.io/smart-contract-best-practices/

The first question which any auditing interview concerns is mostly regarding what is your preferred audit process? Answers could be subjective, but I like to follow the industry standard as in this ‘Solcurity Standard’ article by Rari-Capital along with the Consensys’ best practices set of guidelines which pave a path for a thorough audit process.

Security should always be a major priority when developing smart contracts. Millions of dollars are lost to hackers on what seems like a regular basis. As a Web3 developer, you need to continuously stay up to date on the latest security best practices.

Solidity basics and best practices

Smart Contracts Best Practices