fiftyeightandeight

Merging https://github.com/hirosystems/docs/issues/110 into this PR. What should be done to ask for Stacks API to add support for semi-fungible token (SFT) metadata? > https://github.com/stacksgov/sips/pull/42 is now in the Accepted status,...

We also have a similar issue. It not only makes reading harder but also aesthetically not pleasing. Can we please improve on this?

Option 1 seems simple enough and straightforward. So the only difference between right now and Option 1 is the switch between the first step and the second step (more or...

> Hi all, SIP-013 tokens have to be queried using this URL structure (similar to how an NFT is queried): `/metadata/sft/:contract_id/:token_id`, for example: https://api.hiro.so/metadata/sft/SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.key-alex-autoalex-v1/77050 > > However, I double checked...

I am seeing quite some divergences in inscription number among indexers: 13273849: https://bestinslot.xyz/ordinals/inscription/1372e603f06aaeb88bc3069fdf0a135647d79aa347156973b227511f69689731i0 13273850: https://ordinals.com/inscription/1372e603f06aaeb88bc3069fdf0a135647d79aa347156973b227511f69689731i0 13273199: https://ordinals.hiro.so/inscription/1372e603f06aaeb88bc3069fdf0a135647d79aa347156973b227511f69689731i0 Any chance this relates to the upgrade/fix?

+1 As we look to work more closely with Grant Program to further community integration, help such as what Dio and Vidia are offering will be crucial.

> I'd argue that the **correct** solution is to leave `block-height` as-is, returning the chain length, and then require any contracts to adapt to the new timing of blocks, but...

> > Can we just copy what [Bitcoin](https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki) or [Ethereum](https://chat.openai.com/share/0ebf4c7c-6cb2-4246-b471-75dfb05a66d4) do? > > > > I think that's a good idea. All ethereum's consensus rules do is mandate that a...