Comment by @h4x3rotab • Hey

The separation of post data makes it hard to collect Momoka posts. Collect is a relatively complex action. It would check the prerequisite and mint the NF

Stats

Comments

You may have noticed the hex (0x) numbers in a full publication id. The first number is the profile id, and the second number is the publication id under the profile. For example, my post "0x82a0-0x0d" means the 14th (0x0d) post sent to the 33440th (0x82a0) Lens profile NFT. The publication id increments every time you make a new post. So if I create a new post, it would be "0x82a0-0x0e" (the 15th post). You can identify any post by a combination of the profile id and the publication id on Polygon. This is no longer the case entering the Momoka era. The full publication id becomes longer. The id "0x82a0-0x0d-DA-7e643f4e" doens't refer to the 14th post. Instead, it means a post following the 13th Polygon post on Data Available layer with the id Arweave id "7e643f4e". Since the Lens smart contract is not aware of the Momoka posts, the publication id only increments for every Polygon post. Posting on Momoka cannot increment the on-chain counter. So now you can have multiple posts with the same publication id on Momoka. You can only tell the difference by their arweave tx id. For example, below are my two Momoka posts with the same publication id (0x0d): - https://lenster.xyz/posts/0x82a0-0x0d-DA-7e643f4e - https://lenster.xyz/posts/0x82a0-0x0d-DA-6c6c050b Because of the data separation, the post to Momoka cannot trigger the increment of the publication id in my Lens profile. So to distinguish them, a "DA" prefix with the Arweave tx id must be added to uniquely identify a post on the global scale.