HashPort @Hashport01

Congrats on cross chain miners going live, and thanks to @benson_doge for the idea behind it The miner keeps mining on its original chain while on X Layer it can be listed, rented, split or used as collateral From where HashPort sits, we're thinking about what comes next Miners just became composable assets markets, rentals and lending apps around them are going to show up one by one Every one of those apps has a frontend users sign approvals and listings there against custody contracts The more complex the asset, the less you can afford a swapped signing page That's exactly what we work on publishing frontends on chain, every file with a path and a hash, so you can check the page before you sign Builders shipping apps on top of this, if you want your frontend on chain, come talk to us

Blonskr @Blonskr

21 hours ago

重要功能上线： 今天开始，矿机可以跨链到XLayer了！该功能参考了TapeOut生态第三方开发者 @benson_doge 文章的逻辑，让矿机在原有链上工作，但同一时刻它可以在 XLayer 上被挂单出售、被拆分出租、被抵押，并且能随时将挖到的BEM一键领取到XLayer。

39 24 130 24K 8

This is when we really understood how heavy a word like cohesion is This is a community with a lot of love in it HashPort is staying right here, and we keep going

Blonskr @Blonskr

a day ago

在尚未发布资金管理规则的时候，在尚未发布资金收取地址的时候，在尚未发布资金管理团队人员的时候。亲身参与这一切，才觉得凝聚力这个词是如此的重。感谢这个时代，感谢这些所有人。这只会让我更加努力，奋力前行。

3 1 31 4K 1

Version numbers get typed wrong Hashes don't

Replying to critics a while back, @Blonskr laid out the order PoD → HashPort → TapeKit and TapeSend Our spot on that line is pretty specific TapeOut provides circuits and containers HashPort publishes the frontend into them and registers every file TapeKit reads it back and verifies We take the middle piece and make it solid

We'd suggest thinking of the gateway as an entrance, not the site What you verify against is always the paths and hashes registered on chain

When a wallet shows Official, the draft requires two addresses on screen the contract being checked and where the frontend lives Even with the strongest badge showing take two seconds is that the contract you actually meant to use

An official frontend doesn't have to be just one site The BEP draft lets a contract declare several frontends a primary plus mirrors If a mirror is in the contract's declaration, the wallet sees Official A page that isn't gets flagged as not the frontend the contract declared

A wrong version isn't the real problem Uploading something that was never meant to be public is Keep private keys, API keys, env vars and DB passwords out of dist

Pushed the wrong file by accident, can you take it back The directory, yes update or remove that path and the site points to the new entry right away The old bytes, no, they stay on chain

No badge at all, what does it mean In the BEP draft that's Unbound the domain isn't bound to an onchain frontend so the wallet shows nothing No badge doesn't mean it's bad doesn't mean it's safe either It just means there's nothing on chain to check this page against

Uploading a big file and it looks frozen Check the page log first Each file goes out in one or more transactions big files take several the log shows the chunking progress

What the BEP draft requires no . or .. segments no control characters UTF 8, NFC normalized no leading / Non English filenames are allowed if normalized Honestly, lowercase letters and numbers save you a lot of grief

pathCount for how many paths pathsRange to list them in batches fileInfo for hash, size, type and last update read for the whole file, readRange for big ones in pieces

In the BEP draft, binding a domain to a frontend uses a _frontend TXT record It looks like this v=1 chain=56 store=0x... site=0x... chain is the decimal chain ID, 56 for BNB Chain mainnet store and site are two contract addresses exactly one v=1 record per hostname

So publish the final version read it back and check the hashes update the status page then list

While it's listed the whole site is frozen not a single file can change the buyer gets exactly what was there at listing

Resolution is only cached for 60 seconds Files are addressed by SHA 256, so a new hash means the old cache is dead anyway The viewer also prompts a reload when hashes or file counts change Still old after a minute, check whether you uploaded to a different path

Just pushed a new version and the old one still shows up Give it a minute

Want a little tool that watches a site for updates Don't reach for eth_getLogs dataseed rejects even a 500 block query TapeKit's watch uses plain read calls polling paths, file count and hashes all four public nodes support it Copy that approach and save yourself the pain

Agree with this, adding what we see from the HashPort side What we watch every day isn't the chart it's whether people are still uploading sites into containers Since the drop, the questions we get have changed it used to be when moon now it's how do I upload dist, how do I bind a domain, why doesn't my hash match people asking that stuff are planning to stick around and build Onchain has one nice property every site's paths and hashes will still check out six months from now ours is making publishing solid, so any frontend that wants to go on chain gets up there and reads back clean

币老韭 @xcsm8888

3 days ago

最近 BEM 跌了不少，社区的情绪也明显没有前段时间那么兴奋了。 这很正常。 上涨的时候，所有人看到的都是价格； 下跌的时候，才会真正看清一个社区还剩下什么。 我反而觉得，现在是观察 TapeOut 最有意思的时候。 因为 K 线在跌，但 Builder 没有停。 TapeKit 在继续完善，tape://

6 2 14 4K 1