Locking can be seen as an important positive factor, as the price often reacts immediately after the dev locks up. However, under normal circumstances, it is only after the project's official Twitter account announces the locking details and link that the locking situation becomes known. So how can we proactively know if the dev has locked up and the actual locking details?
Let's use $sora (89nnWMkWeF9LSJvAWcN2JFQfeWdDk6diKEckeToEU1hE) as an example for explanation. When locking up, the dev will transfer the tokens to the locking contract. Here we need to check the transfer operations of the dev address, and which tool can conveniently view the transfer operations? I chose debot.
The debot team previously operated the diting monitoring tool for a few years, and now has expanded to @DitingData, enriching the product features with trading, data analysis and other functions. The website is https://debot.ai. The reason I didn't choose gmgn, xxyy or bullx is that these websites don't list the transfer operations, and I would have to go to solscan to find the specific transfer transactions based on the dev's address.
Opening debot and entering the ca, we can see all the operations of this dev in the "Developers" section at the bottom (as shown in 1 in the image). The $sora dev first bought and sold once, and then bought 100M tokens, which he transferred in two batches (as shown in 2 in the image). We can check what these two transfers were for. We can click the icon shown in 3, which is the link to this transaction, and it will jump to solscan.
Opening the 99.2M transfer (https://solscan.io/tx/NsEGHgmvk4a8YKfXABwzWAxceQfgXJdTJjgxQK1UNAqXTKB6TPDmNnkGRCfssC8ny4eXXRSLjkrYwFtcoVFxGJR), we can see in the details that there is a "Streamflow" marker, which refers to the Streamflow contract address on Solana. Streamflow is a common locking website on Solana. Seeing this marker, we know that this transaction is for locking, but the locking details are not visible here, as we need to go to the Streamflow website to view them.
Copy the address in 1 of the image, and replace the "address" in "https://app.streamflow.finance/contract/solana/mainnet/address" with the address in 1, which becomes https://app.streamflow.finance/contract/solana/mainnet/29yU8G68MPkmrXBzpd89rA1Rw7CBQ4kxWQGnxPSX8yM8. Opening this link, we can see the details.
In the upper right part of the image, we can see that the locking start time is 1.15 10:08 and the unlock time is 3.12 10:08. The lower part shows the locking details, with the unlocked amount being 0, indicating that the entire 99M tokens have been locked. The locking method and amount show that 24.75M tokens will be unlocked every 2 weeks, with the next unlock time being 1.29 10:08, exactly 2 weeks later.
Through the above analysis, we can know the specific details of the dev's first 99.2M transfer for locking, and we can also check the official Twitter announcement.
The official Twitter announcement about 6 months of locking has two inaccuracies:
1. The locking time we analyzed above is 2 months, not the 6 months announced by the official Twitter.
2. The actual locking is a linear unlock, with 24.75M tokens unlocked every 2 weeks, for a total of 99M tokens, 4 times of unlocking, exactly 2 months. This important information was not mentioned at all in the official Twitter.
The dev also had a 829.6K transfer out, which was not announced by the official Twitter. We can also open this transfer record for analysis (https://solscan.io/tx/4CF8AzLcMFsVjWUvqaWqc2hpjdqh3J2QPNNmPSLqNVty9CgQi8yo7BSqt8UC76hdeH9BfRuTEScw9SQJ4t2T3ZHM), which shows that the dev also transferred these tokens to the Streamflow contract.
We can see from the image that the "unlocked" marker is green, and the unlocked token amount is 828.04K, with the locked amount being 0, indicating that the dev simply transferred the tokens to the Streamflow contract without actually locking them. If we don't do a careful analysis, we wouldn't know this.
The above has detailed how to analyze whether the dev's transfers are real locking and the specific locking details based on the dev's address transfers. If we want to know as soon as possible whether the dev has transferred, we need to monitor the dev's address, so that we can discover it in the first time. Speaking of monitoring, I continue to recommend debot, as it has the most comprehensive functions among the tools I have used.
