Return Sablier Logo SVG in NFT descriptor

[PaulRBerg]

Between nothing and the Sablier logo, it'd be better to display the latter.

The SVG logo can be obtained from https://github.com/sablier-labs/branding.

[andreivladbrg]

Fantastic idea 💡

[andreivladbrg]

Which one do you think would be the best? @razgraf I would appreciate your expert opinion on this matter.

Out of all the options, I find these three the most appropriate, and personally I prefer the first one. wdyt?

1	2	3

[razgraf]

Right. So I would actually use something like this, more of a "teaser" rather than the colorful logo.

The image in this post is an actual svg so you can extract the code from it or simply apply Dark000 / #14161F for background and use the tracing for the icon we already have in our lockup design.

I will try to work on our NFT design towards December as the app enters the testing phase.

[PaulRBerg]

Thanks for your advice @razgraf.

more of a "teaser" rather than the colorful logo

Agree. Also, a square image would work better on OpenSea.

I will try to work on our NFT design towards December as the app enters the testing phase.

Don't worry — let's do that only if the NFT feature picks up steam. Related: https://github.com/sablier-labs/company-discussions/discussions/30#discussioncomment-10548890

[andreivladbrg]

I would actually use something like this, more of a "teaser" rather than the colorful logo

thanks for the quick answer. agree with this, it would be better.

for background and use the tracing for the icon we already have in our lockup design

i've gotten this svg:

<svg width="500" height="500" style="background-color: #14161F;" xmlns="http://www.w3.org/2000/svg" viewBox="0 -400 210 1000">
  <path id="Logo" fill="#fff" fill-opacity="1" d="m133.559,124.034c-.013,2.412-1.059,4.848-2.923,6.402-2.558,1.819-5.168,3.439-7.888,4.996-14.44,8.262-31.047,12.565-47.674,12.569-8.858.036-17.838-1.272-26.328-3.663-9.806-2.766-19.087-7.113-27.562-12.778-13.842-8.025,9.468-28.606,16.153-35.265h0c2.035-1.838,4.252-3.546,6.463-5.224h0c6.429-5.655,16.218-2.835,20.358,4.17,4.143,5.057,8.816,9.649,13.92,13.734h.037c5.736,6.461,15.357-2.253,9.38-8.48,0,0-3.515-3.515-3.515-3.515-11.49-11.478-52.656-52.664-64.837-64.837l.049-.037c-1.725-1.606-2.719-3.847-2.751-6.204h0c-.046-2.375,1.062-4.582,2.726-6.229h0l.185-.148h0c.099-.062,.222-.148,.37-.259h0c2.06-1.362,3.951-2.621,6.044-3.842C57.763-3.473,97.76-2.341,128.637,18.332c16.671,9.946-26.344,54.813-38.651,40.199-6.299-6.096-18.063-17.743-19.668-18.811-6.016-4.047-13.061,4.776-7.752,9.751l68.254,68.371c1.724,1.601,2.714,3.84,2.738,6.192Z" transform="scale(1.5, 1.5)" />
</svg>

which results in this image:

lmk if it looks good.

a square image would work better on OpenSea

good point

[andreivladbrg]

Two more questions:

• Should it be the same JSON format as in lockup, with attributes/trait types, etc? (I assume not, until we have the actual NFT SVG)
• Should it be encoded in Base64, or should the logo SVG string simply be returned?

[PaulRBerg]

1. No. No attributes.
2. I don't know. Can you figure it out on your own?