ETHOnline 2023 is in the books! There were a lot of teams that built on Tableland…77 total, in fact. The judging process took quite some time, and although we wanted to reward everyone for their efforts, we ended up distributing 4 "top" prizes for first, second, and two runner up bounties, and then an additional 20 teams also split the pool. We also had a small pool for the teams that built with the (experimental) Basin CLI.
Here'a quick overview of the top projects:
1st place: Zuko—zk privacy social dapp where all logic (likes, comments, etc.) is stored in tables.
2nd place: Vibecheck—a web3 game that stores GPT-generated character attributes and certain game data in Tableland.
Runner up: Web3Agent—use AI/LLM agent to deploy contracts, send txs, ask web3 questions…and use Tableland for saving/querying chat history.
Runner up: Deano—marketplace for ML models to train datasets and get feedback from users in an open community market.
Now, we're off to the Dataverse hackathon, which kicks off on November 9th and runs for about a month. See y'all there!
Optimism Goerli fixes in the SDK
During ETHOnline, we uncovered a bug in the SDK that affected downstream usage in clients like the Studio and even the CLI tool. Basically, Tableland has a devnet / "staging" environment for the Optism Goerli testnet, which is only used internally for testing purposes on a live network. Then, there's an Optimism Goerli testnet deployment that is open for anyone to use as they would any other chain that Tableland supports.
The problem was that the SDK didn't properly filter out the "staging" environment, so SDK users had no way to specify the correct Optimism Goerli chain. For example, if you used the Studio to deploy a table to Optimism Goerli, it created the table on the staging contract, and subsequent SDK APIs don't treat that data the same because it's materialized / exposed at a custom staging gateway.
Anyways, the change is now fixed with @tableland/sdk@4.3.5, the Tableland CLI has this change incorporated, and the Studio will be releasing broader changes the include fix in the near term.
Wrapping up ETHOnline
by Dan Buchholz
ETHOnline 2023 is in the books! There were a lot of teams that built on Tableland…77 total, in fact. The judging process took quite some time, and although we wanted to reward everyone for their efforts, we ended up distributing 4 "top" prizes for first, second, and two runner up bounties, and then an additional 20 teams also split the pool. We also had a small pool for the teams that built with the (experimental) Basin CLI.
Here'a quick overview of the top projects:
Now, we're off to the Dataverse hackathon, which kicks off on November 9th and runs for about a month. See y'all there!
Optimism Goerli fixes in the SDK
During ETHOnline, we uncovered a bug in the SDK that affected downstream usage in clients like the Studio and even the CLI tool. Basically, Tableland has a devnet / "staging" environment for the Optism Goerli testnet, which is only used internally for testing purposes on a live network. Then, there's an Optimism Goerli testnet deployment that is open for anyone to use as they would any other chain that Tableland supports.
The problem was that the SDK didn't properly filter out the "staging" environment, so SDK users had no way to specify the correct Optimism Goerli chain. For example, if you used the Studio to deploy a table to Optimism Goerli, it created the table on the staging contract, and subsequent SDK APIs don't treat that data the same because it's materialized / exposed at a custom staging gateway.
Anyways, the change is now fixed with
@tableland/sdk@4.3.5, the Tableland CLI has this change incorporated, and the Studio will be releasing broader changes the include fix in the near term.From SyncLinear.com | NOT-63