rishitesh mishra @rishitesh

@kshashi Let’s start a ranking of the BS rankings.

🇮🇳 Good morning India! A lot of you asked for full-length mock JEE Main tests in @GeminiApp at no cost - done! Good luck on your prep! Last week, SAT. This week, JEE. What other global exams would be most helpful?

#PuneGrandTour Cyclists speeding down Senapati Bapat Road! I guess at 60 kmph or higher. Excellent cheering crowds all across the 95 km race route through Pune today. (Excellent video by Sameer Kanade - via @abhijitathavale) @PuneGrandTour

#PuneGrandTour Graceful, fast turn at Law College Road, onto Prabhat Road... Look at the speed of cyclists! Plenty of cheering crowds. (Great capture by Abhijit Ambike - video via @abhijitathavale) @PuneGrandTour

Pune will always surprise you!! 70 years old Kaka steals the show 🔥

@aparanjape They don't even warn you about it using markers or reflectors, be it on a highway or within PMC limits. It's criminal negligence.

Software engineering is 90% database and 10% frontend.

Congratulations @DhruvaSpace

Dhruva Space @DhruvaSpace

12 months ago

Our LEAP-1 satellite aboard the #SpaceX Falcon 9 rocket! Make us proud!

keyboard_arrow_left Previous keyboard_arrow_right Next

8 61 982 21K 28

Language verbosity is a blessing in disguise. While some devs may not like it when writing a solution, you'll surely appreciate it when reading someone else's code. In non-trivial software projects, development is more about reading than writing.

BREAKING: 🇮🇳 RBI approves blockchain-based MSME financing solution by IBDIC, backed by ICICI, HDFC, Yes Bank & Aditya Birla Capital. 💡 Uses tokenised invoices to give small suppliers faster, cheaper credit. 📌 Now available for adoption by regulated entities.

keyboard_arrow_left Previous keyboard_arrow_right Next

@JioHotstar @SonySportsNetwk Here is an idea, use AI to provide live sports commentary subtitle, making your platform more inclusive. You have a finite set of commentators and models can easily be trained for their voices.

.@spaceandtime—a layer-1 blockchain for ZK-proven data and the first Build team to be a part of Chainlink Rewards—is a title sponsor of this year's SmartCon. Secure your tickets today ⬇️

@smtgpt Well done @smtgpt & team !!. Step by step let's defeat this evil..

@chiefbuidl Are you sure ? about 10 years .. :)

India's government announced that its military had killed the terrorist who beheaded Jewish-American journalist Daniel Pearl. jpost.com/breaking-news/…

𝗪𝗵𝗮𝘁 𝘁𝗵𝗲 𝗵𝗲𝗰𝗸 𝗶𝘀 𝗦𝗽𝗮𝗰𝗲 𝗮𝗻𝗱 𝗧𝗶𝗺𝗲? 🚀⏳ GM Gigabrains! @spaceandtime is a specialized blockchain designed to securely store and verify database inserts using cryptographic proofs directly onchain. It leverages a newly invented Zero-Knowledge (ZK) proof specifically tailored for SQL. This enables smart contracts on Ethereum (and compatible chains) to trustlessly access verified, tamperproof query results. You could think of Space and Time as the first cryptographically tamperproof (trustless) database. It consists of three core components: 1. 𝗜𝗻𝗱𝗲𝘅𝗲𝗿 𝗡𝗼𝗱𝗲𝘀: Lightweight servers that continuously gather and transform blockchain data from Ethereum, major Layer 2s, Sui, etc. They index, sign, and forward this data securely to the validators. 2. 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗼𝗿 𝗡𝗼𝗱𝗲𝘀 (𝗦𝗫𝗧 𝗖𝗵𝗮𝗶𝗻): The decentralized blockchain itself—these globally distributed nodes use Byzantine Fault Tolerance (BFT) consensus to validate new data entries, creating cryptographic hashes that guarantee each database table remains cryptographically tamperproof. The trustless tables secured by SXT chain can contain verifiably indexed data from your smart contracts (inserted by the network of indexer nodes with consensus), zkTLS data inserted from consumers, or even your own offchain data to be signed and inserted... with SXT chain capturing the verified signatures on insert. 3. 𝗣𝗿𝗼𝘃𝗲𝗿 𝗡𝗼𝗱𝗲𝘀: NVIDIA GPU servers that run our Proof of SQL protocol, generating zero-knowledge proofs. These proofs allow Ethereum-based smart contracts to verify database query results without trusting any middleman. These queries can be against indexed data from smart contract events on your own chain, other chains, or customers' offchain data inserted with signatures or zkTLS proofs. Additionally, @MakeInfiniteCo offers a scalable managed database built on Apache Spark, containing accurately indexed blockchain data from SXT Chain itself, Ethereum, Bitcoin, ZKsync Era, Base, Arbitrum, Sui, and more. This database enables fast analytics and dashboards via REST APIs—perfect for frontend applications that don’t require the additional security of ZK-proven SQL. 📈📊

@iNikhilsaini Indeed beautiful place, also safe.

SUNNY G GOT MOVES AT 75 AGE. 😂🔥 Sunil Gavaskar playing with Champak. 🐕

I was honestly shocked in 2020 to find out that smart contracts have no way to ask basic questions about the users that interact with smart contracts. There is no onchain database in the EVM. What??? 🤯 With traditional apps, there is almost always a database that powers basic app decisions. Apps adjust user experience based on past interactions stored in the database. The problem with crypto is that although you CAN store users' past onchain interactions in a database, you CANNOT have a trusted database powering your dapp (app with smart contracts as the backend), because the database owners could cheat and return false query results onchain to the dapp's contracts. Adding a decentralized oracle network in between (to send query results to a smart contract ad hoc) doesn't solve this, unfortunately. It becomes especially problematic if the query results are used to move a lot of money onchain. For example, if a liquid staking protocol has a daily rebasing of shares, and this rebasing is determined by query results around data tables containing user transfers of the LST, an insider with access to the database could just change one row of data and give themselves millions of dollars of the LST. Although a decentralized oracle delivers the daily rebasing query results to the liquid staking protocol's contracts, the source database remains a "tamper-able" root of trust. Not good. 😬 Here's another one: if you're claiming an airdrop based on your onchain activity/history (usually indexed data in a database) and a query result determines your airdrop allocation, insiders with access to the database can just add their own wallets with an outsized/unfair allocation. We see this all too often. 😞 Okay, last example: a lending protocol might want to adjust borrow rates based on borrower's loan payoff/liquidation history. An insider could just add a few rows to a database table and create a false loan payoff history to give themselves a unfairly low borrow rate, etc. 🤦‍♂️ With this in mind, the team at @spaceandtime set out in 2021 to begin building the first trustless database for the EVM: delivering crazy fast ZK-proven SQL query results to dev's smart contracts, proving that both the query result and the underlying tables of indexed EVM event data (unchain user activity/history) have not been tampered. Sub-second ZK proofs will change the industry forever. Imagine ZK-proving all the world's SQL databases. Imagine a journey through Space and Time 🚀⏳