royalty-registry-solidity VS Nest

https://opensea.io/collection/1989-sisters. As part of that project, I contributed to the open source Manifold royalty registry to patch an migration issue with OpenSea contracts that allowed for them to receive payments through Coinbase NFT: https://github.com/manifoldxyz/royalty-registry-solidity/pul....

Spending most of my time now back in Ruby/Rails, Docker, AWS and overseeing a small team of iOS developers and QA engineers based in eastern Europe (Ukraine as it happens). Also serving as our de facto product manager and designer and have handled all UI/UX/Iconography design in Figma. Extensive work with Plaid, multi-docker container deployments (AWS ECS/Fargate), subscription payments, etc. Fast learner and take pride in my craft.

Feel free to contact me. I'm happy to send work samples. Need to touch up my resume/portfolio/website but am posting here in the meantime. Thanks!

email: p dot osetinsky at gmail dot com

To solve this issue, a consortium of major NFT marketplaces around manifold.xyz agreed to deploy an industry-wide registry contract that collection builders can use to signal royalty splits independently from their token contracts. The Royalty Registry’s open source code base reveals that it supports many of the most important marketplace interfaces.

When using the NestJS framework, sometimes you may need to change some default timeout. You can define them just like you'd do in a plain Node.js HTTP server like so:

Back: a graphQL server built with Nestjs

NestJS - opinionated more scalable, but harder to learn docs

Pragmatically, we can apply this to a Nest application by creating an Interface for our services, separating the Presenter layer (Controller) from the Use Case (Services):

It’s a text document that contains all the commands a user could call to assemble an image. Let’s check an example of a Dockerfile for a nodejs app in this case it will be a NestJS app and then explain each part.

describe('Create bookmarks', () => { const dto: CreateBookmarkDto = { title: 'NestJS', link: 'https://nestjs.com/', }; it('should create bookmark', () => { return pactum .spec() .post('/bookmarks') .withHeaders({ Authorization: 'Bearer $S{userAt}', }) .withBody(dto) .expectStatus(201) .stores('bookmarkId', 'id')//store the bookmark id in the variable bookmarkId .expectBodyContains(dto.title) .expectBodyContains(dto.link) }); });

In my usual NodeJS tech stack, which includes GraphQL, NestJS, SQL (predominantly PostgreSQL with MikroORM), I encountered these limitations. To overcome them, I've developed a new stack utilizing Rust, which still offers some ease of development:

The purpose of this article is to provide a step-by-step guide for implementing authentication system in a NestJS project using the Passport middleware module.

That's exactly where I am. My manager gave me these links, that cover a lot of those words the backend uses, so I can identify what they mean and how to use them. 1. For inspiration and concepts: https://github.com/Sairyss/domain-driven-hexagon 2. Suggested to read the documentation for nest.js. They apply such concepts I don't understand: https://nestjs.com/