<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mahesh Kandegedara on Medium]]></title>
        <description><![CDATA[Stories by Mahesh Kandegedara on Medium]]></description>
        <link>https://medium.com/@maheshhasantha?source=rss-1576ad9fb1ea------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*mz4viA2EplltmjAl.</url>
            <title>Stories by Mahesh Kandegedara on Medium</title>
            <link>https://medium.com/@maheshhasantha?source=rss-1576ad9fb1ea------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:18:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maheshhasantha/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NestJS Fundamentals]]></title>
            <link>https://medium.com/@maheshhasantha/nestjs-fundamentals-3d994cf89fd1?source=rss-1576ad9fb1ea------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d994cf89fd1</guid>
            <category><![CDATA[bootcamp]]></category>
            <category><![CDATA[nestjs]]></category>
            <category><![CDATA[nestjs-tutorial]]></category>
            <dc:creator><![CDATA[Mahesh Kandegedara]]></dc:creator>
            <pubDate>Wed, 06 May 2026 19:54:06 GMT</pubDate>
            <atom:updated>2026-05-06T19:54:06.665Z</atom:updated>
            <content:encoded><![CDATA[<p>One-Day Bootcamp · Corporate Training Edition</p><p><a href="https://mahesh2009.github.io/nestjs/README.html">NestJS Fundamentals</a></p><p>⏱ Full Day · ~7.5 hrs🎯 Technical Audience💻 Hands-On Labs📖 Case Study DrivenNode.js 20+ · NestJS 10+</p><h3>📋 Today’s Case Study</h3><h3>DevTask API — A Developer Team Task Management System</h3><p>You are a backend engineer at a growing tech startup. The CTO has asked you to build an internal REST API that engineering teams can use to track tasks, manage users, and monitor project progress. You will build this system from scratch today, adding a new layer with every NestJS concept you learn.</p><h3>📅 Day Schedule</h3><p>09:00</p><p>Module 1Intro, Setup &amp; Project Structure</p><p>10:00</p><p>Module 2Controllers &amp; Routing</p><p>11:00</p><p>☕ Break (15 min)</p><p>11:15</p><p>Module 3Providers &amp; Dependency Injection</p><p>12:15</p><p>Module 4Modules &amp; Application Structure</p><p>13:00</p><p>🍽 Lunch (45 min)</p><p>13:45</p><p>Module 5DTOs, Pipes &amp; Validation</p><p>14:45</p><p>Module 6Exception Filters</p><p>15:30</p><p>☕ Break (15 min)</p><p>15:45</p><p>Module 7Guards</p><p>16:30</p><p>Module 8Interceptors &amp; Middleware</p><p>17:15</p><p>Wrap-UpFinal challenge &amp; Q&amp;A</p><p>1</p><h3>Introduction, Setup &amp; Project Structure</h3><p>60 min</p><p><strong>📖 Concept</strong></p><h3>What is NestJS?</h3><p>NestJS is a progressive Node.js framework built with TypeScript that brings architectural patterns familiar from enterprise Java (Spring Boot, Angular) into the Node ecosystem. It uses decorators, dependency injection, and a modular architecture to produce maintainable, testable, and scalable server-side applications.</p><p>Why NestJS over plain Express? Express gives you routing. NestJS gives you architecture — a consistent way to organise code that scales across teams and months of development.</p><h3>Core Building Blocks</h3><p>Request │ ▼ Middleware ──► Guards ──► Interceptors ──► Pipes │ ▼ Controller ──► Service ──► Repository │ ▼ Interceptors (response) │ ▼ Exception Filters (on error)</p><p>Building BlockResponsibilityDecoratorControllerHandle HTTP requests, define routes@Controller()Provider / ServiceBusiness logic, injectable dependencies@Injectable()ModuleOrganise and group related code@Module()MiddlewarePre-processing of requestsClass or functionGuardAuthorization — can this request proceed?@UseGuards()PipeValidation and transformation of input@UsePipes()InterceptorWrap request/response logic@UseInterceptors()Exception FilterHandle and transform errors@UseFilters()</p><h3>Project File Structure</h3><p>DevTask API — target structure</p><pre>src/<br>├── main.ts                    ← Bootstrap entry point<br>├── app.module.ts              ← Root module<br>├── tasks/<br>│   ├── tasks.module.ts        ← Feature module<br>│   ├── tasks.controller.ts    ← Route handlers<br>│   ├── tasks.service.ts       ← Business logic<br>│   ├── dto/<br>│   │   ├── create-task.dto.ts<br>│   │   └── update-task.dto.ts<br>│   └── entities/<br>│       └── task.entity.ts<br>└── common/<br>    ├── filters/<br>    │   └── http-exception.filter.ts<br>    ├── guards/<br>    │   └── api-key.guard.ts<br>    └── interceptors/<br>        └── logging.interceptor.ts</pre><p><strong>💻 Hands-On — Scaffold DevTask API</strong></p><p>1</p><p>Install the NestJS CLI globally</p><pre>npm install -g @nestjs/cli<br>nest --version   # should print 10.x.x</pre><p>2</p><p>Create the project</p><pre>nest new devtask-api<br>cd devtask-api<br>npm run start:dev   # starts on http://localhost:3000</pre><p>Hit http://localhost:3000 — you should see Hello World!</p><p>3</p><p>Explore the generated files</p><p>Open src/app.module.ts, src/app.controller.ts, and src/main.ts. Notice:</p><ul><li>NestFactory.create(AppModule) — the entry point wires everything together</li><li>@Module() decorator connects controllers and providers</li><li>@Controller() and @Get() define the route</li></ul><p>4</p><p>Scaffold the Tasks feature module</p><pre>nest generate module tasks<br>nest generate controller tasks<br>nest generate service tasks</pre><p>Check app.module.ts — NestJS automatically imported TasksModule.</p><p>5</p><p>Create the Task entity interface</p><p>src/tasks/entities/task.entity.ts</p><pre>export enum TaskStatus {<br>  OPEN = &#39;OPEN&#39;,<br>  IN_PROGRESS = &#39;IN_PROGRESS&#39;,<br>  DONE = &#39;DONE&#39;,<br>}</pre><pre>export interface Task {<br>  id: string;<br>  title: string;<br>  description: string;<br>  status: TaskStatus;<br>  createdAt: Date;<br>}</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>Which NestJS building block is responsible for <em>authorization</em> — deciding whether a request should proceed?</p><ul><li>Middleware</li><li>Interceptor</li><li>Guard</li><li>Pipe</li></ul><p>Question 2</p><p>In the NestJS request lifecycle, what runs <em>before</em> Guards?</p><ul><li>Pipes</li><li>Middleware</li><li>Interceptors</li><li>Exception Filters</li></ul><p>Question 3</p><p>What does nest generate module tasks automatically do to app.module.ts?</p><p>2</p><h3>Controllers &amp; Routing</h3><p>60 min</p><p><strong>📖 Concept</strong></p><h3>What is a Controller?</h3><p>Controllers handle incoming HTTP requests and return responses. They define the route structure of your API using decorators. A controller should only handle routing and input extraction — all business logic belongs in a service.</p><h3>Key Route Decorators</h3><p>DecoratorHTTP MethodUsage@Get(path?)GETRetrieve resources@Post(path?)POSTCreate resources@Put(path?)PUTReplace a resource@Patch(path?)PATCHPartial update@Delete(path?)DELETERemove a resource</p><h3>Parameter Decorators</h3><p>DecoratorExtracts@Param(&#39;id&#39;)Route parameter (/tasks/:id)@Body()Request body (parsed JSON)@Query(&#39;status&#39;)Query string param (?status=OPEN)@Headers(&#39;x-api-key&#39;)Request header value@Req()Full Express request object</p><h3>HTTP Status Codes</h3><p>NestJS returns 200 for GET/DELETE/PATCH and 201 for POST by default. Override with @HttpCode(204).</p><pre>@Post()<br>@HttpCode(HttpStatus.CREATED)  // explicit, but 201 is default for POST<br>async create(@Body() dto: CreateTaskDto): Promise&lt;Task&gt; { ... }</pre><p><strong>💻 Hands-On — Build the TasksController</strong></p><p>1</p><p>Update TasksController with all CRUD routes src/tasks/tasks.controller.ts</p><pre>import {<br>  Controller, Get, Post, Patch, Delete,<br>  Param, Body, Query, HttpCode, HttpStatus,<br>} from &#39;@nestjs/common&#39;;<br>import { TasksService } from &#39;./tasks.service&#39;;<br>import { Task, TaskStatus } from &#39;./entities/task.entity&#39;;</pre><pre>@Controller(&#39;tasks&#39;)<br>export class TasksController {<br>  constructor(private readonly tasksService: TasksService) {}</pre><pre>  // GET /tasks<br>  // GET /tasks?status=OPEN<br>  @Get()<br>  findAll(@Query(&#39;status&#39;) status?: TaskStatus): Task[] {<br>    return this.tasksService.findAll(status);<br>  }</pre><pre>  // GET /tasks/:id<br>  @Get(&#39;:id&#39;)<br>  findOne(@Param(&#39;id&#39;) id: string): Task {<br>    return this.tasksService.findOne(id);<br>  }</pre><pre>  // POST /tasks<br>  @Post()<br>  create(@Body() body: { title: string; description: string }): Task {<br>    return this.tasksService.create(body.title, body.description);<br>  }</pre><pre>  // PATCH /tasks/:id/status<br>  @Patch(&#39;:id/status&#39;)<br>  updateStatus(<br>    @Param(&#39;id&#39;) id: string,<br>    @Body(&#39;status&#39;) status: TaskStatus,<br>  ): Task {<br>    return this.tasksService.updateStatus(id, status);<br>  }</pre><pre>  // DELETE /tasks/:id<br>  @Delete(&#39;:id&#39;)<br>  @HttpCode(HttpStatus.NO_CONTENT)<br>  remove(@Param(&#39;id&#39;) id: string): void {<br>    this.tasksService.remove(id);<br>  }<br>}</pre><p>2</p><p>Test with curl or Postman</p><pre># Create a task<br>curl -X POST http://localhost:3000/tasks \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;Set up CI/CD&quot;,&quot;description&quot;:&quot;Configure GitHub Actions pipeline&quot;}&#39;</pre><pre># List all tasks<br>curl <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a></pre><pre># Filter by status<br>curl &quot;http://localhost:3000/tasks?status=OPEN&quot;</pre><p>The service methods don’t exist yet — you’ll implement them in Module 3. The server will error until then.</p><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>You want to extract ?assignee=john from the URL in a controller method. Which decorator do you use?</p><ul><li>@Param(&#39;assignee&#39;)</li><li>@Query(&#39;assignee&#39;)</li><li>@Body(&#39;assignee&#39;)</li><li>@Headers(&#39;assignee&#39;)</li></ul><p>Question 2</p><p>A DELETE /tasks/:id endpoint should return no body. What status code and decorator should you use?</p><p>Question 3</p><p>What is wrong with this controller method?</p><pre>@Get(&#39;:id&#39;)<br>findOne(@Param(&#39;id&#39;) id: string) {<br>  const result = this.db.query(`SELECT * FROM tasks WHERE id = ${id}`);<br>  return result;<br>}</pre><p><strong>🔁 Practice</strong></p><p>Challenge</p><p>Add a GET /tasks/stats route that returns the count of tasks in each status. Consider: where should this route be placed relative to GET /tasks/:id and why?</p><p>Hint: Route order matters in NestJS. /tasks/stats placed after /tasks/:id would match :id = &quot;stats&quot; instead of the stats route. Place specific routes before parameterised ones.</p><p>☕ Morning Break — 15 minutes</p><p>3</p><h3>Providers &amp; Dependency Injection</h3><p>60 min</p><p><strong>📖 Concept</strong></p><h3>What is a Provider?</h3><p>A provider is any class annotated with @Injectable(). NestJS manages its lifecycle and can inject it into any other class that declares it as a constructor dependency. This is the Dependency Injection (DI) pattern.</p><p>DI in one sentence: Instead of a class creating its own dependencies with new, it declares what it needs and the framework provides it — making code testable and decoupled.</p><h3>Provider Scopes</h3><p>ScopeBehaviourUse CaseDEFAULT (Singleton)One instance per applicationServices, repositories (default)REQUESTNew instance per requestRequest-scoped stateTRANSIENTNew instance per consumerLightweight, stateless utilities</p><h3>Custom Providers</h3><p>Beyond simple classes, NestJS supports value providers, factory providers, and alias providers for advanced DI scenarios:</p><pre>// Value provider — inject a config object<br>{ provide: &#39;APP_CONFIG&#39;, useValue: { maxTasks: 100 } }</pre><pre>// Factory provider — computed at bootstrap<br>{ provide: &#39;DB_CONNECTION&#39;, useFactory: () =&gt; createConnection() }</pre><pre>// Alias — inject one token as another<br>{ provide: TasksService, useExisting: CachedTasksService }</pre><p><strong>💻 Hands-On — Implement TasksService</strong></p><p>1</p><p>Build the in-memory TasksService src/tasks/tasks.service.ts</p><pre>import { Injectable, NotFoundException } from &#39;@nestjs/common&#39;;<br>import { Task, TaskStatus } from &#39;./entities/task.entity&#39;;<br>import { v4 as uuid } from &#39;uuid&#39;;</pre><pre>@Injectable()<br>export class TasksService {<br>  private tasks: Task[] = [];</pre><pre>  findAll(status?: TaskStatus): Task[] {<br>    if (status) {<br>      return this.tasks.filter((t) =&gt; t.status === status);<br>    }<br>    return this.tasks;<br>  }</pre><pre>  findOne(id: string): Task {<br>    const task = this.tasks.find((t) =&gt; t.id === id);<br>    if (!task) {<br>      throw new NotFoundException(`Task with ID &quot;${id}&quot; not found`);<br>    }<br>    return task;<br>  }</pre><pre>  create(title: string, description: string): Task {<br>    const task: Task = {<br>      id: uuid(),<br>      title,<br>      description,<br>      status: TaskStatus.OPEN,<br>      createdAt: new Date(),<br>    };<br>    this.tasks.push(task);<br>    return task;<br>  }</pre><pre>  updateStatus(id: string, status: TaskStatus): Task {<br>    const task = this.findOne(id);  // reuses findOne — throws if not found<br>    task.status = status;<br>    return task;<br>  }</pre><pre>  remove(id: string): void {<br>    this.findOne(id);  // throws NotFoundException if missing<br>    this.tasks = this.tasks.filter((t) =&gt; t.id !== id);<br>  }<br>}</pre><p>2</p><p>Install uuid</p><pre>npm install uuid<br>npm install -D @types/uuid</pre><p>3</p><p>Run a full CRUD test</p><pre># Create two tasks<br>curl -X POST http://localhost:3000/tasks -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;Write unit tests&quot;,&quot;description&quot;:&quot;Cover service layer&quot;}&#39;</pre><pre>curl -X POST <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a> -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;Code review&quot;,&quot;description&quot;:&quot;Review open PRs&quot;}&#39;</pre><pre># List all — note the IDs<br>curl <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a></pre><pre># Update status (replace ID)<br>curl -X PATCH http://localhost:3000/tasks/&lt;ID&gt;/status \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;status&quot;:&quot;IN_PROGRESS&quot;}&#39;</pre><pre># Delete<br>curl -X DELETE http://localhost:3000/tasks/&lt;ID&gt;</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>What happens if you remove @Injectable() from TasksService?</p><ul><li>The service still works because TypeScript handles injection</li><li>NestJS throws a runtime error when resolving dependencies</li><li>The service is instantiated as a singleton without DI</li><li>Nothing — @Injectable() is optional</li></ul><p>Question 2</p><p>In TasksService.findOne() we throw NotFoundException. Where does this get caught and converted to a 404 HTTP response?</p><p>Question 3</p><p>If TasksService is DEFAULT scope (singleton), and 1,000 concurrent requests hit your API, how many instances of TasksService exist?</p><p>4</p><h3>Modules &amp; Application Architecture</h3><p>45 min</p><p><strong>📖 Concept</strong></p><h3>What is a Module?</h3><p>Modules are the primary organisational unit in NestJS. Every application has at least one root module (AppModule). Feature modules encapsulate related controllers, services, and other providers into a cohesive unit.</p><pre>@Module({<br>  imports: [],       // other modules whose exported providers you need<br>  controllers: [],   // controllers that belong to this module<br>  providers: [],     // services and providers instantiated by this module<br>  exports: [],       // providers made available to importing modules<br>})</pre><p>Rule of thumb: If a service is only used inside one module, keep it private (don’t export it). Only export what other modules genuinely need.</p><h3>Shared Modules vs Global Modules</h3><p>Mark a module @Global() to make its exports available everywhere without importing it — useful for logging, config, or database connections. Use sparingly.</p><p><strong>💻 Hands-On — Add a Users Module</strong></p><p>1</p><p>Generate Users module</p><pre>nest generate module users<br>nest generate controller users<br>nest generate service users</pre><p>2</p><p>Create a basic UsersService that TasksService can reference src/users/users.service.ts</p><pre>import { Injectable } from &#39;@nestjs/common&#39;;</pre><pre>export interface User { id: string; username: string; }</pre><pre>@Injectable()<br>export class UsersService {<br>  private users: User[] = [<br>    { id: &#39;u1&#39;, username: &#39;alice&#39; },<br>    { id: &#39;u2&#39;, username: &#39;bob&#39; },<br>  ];</pre><pre>  findByUsername(username: string): User | undefined {<br>    return this.users.find((u) =&gt; u.username === username);<br>  }<br>}</pre><p>3</p><p>Export UsersService from UsersModule so TasksModule can use it src/users/users.module.ts</p><pre>@Module({<br>  controllers: [UsersController],<br>  providers: [UsersService],<br>  exports: [UsersService],   // ← makes UsersService available to other modules<br>})<br>export class UsersModule {}</pre><p>4</p><p>Import UsersModule into TasksModule src/tasks/tasks.module.ts</p><pre>@Module({<br>  imports: [UsersModule],   // ← now TasksService can inject UsersService<br>  controllers: [TasksController],<br>  providers: [TasksService],<br>})<br>export class TasksModule {}</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>You add UsersService to TasksModule.providers instead of importing UsersModule. What is the problem?</p><p>Question 2</p><p>When should you use @Global()?</p><p>🍽 Lunch Break — 45 minutes</p><p>5</p><h3>DTOs, Pipes &amp; Validation</h3><p>60 min</p><p><strong>📖 Concept</strong></p><h3>What is a DTO?</h3><p>A Data Transfer Object is a class that defines the shape and validation rules of data flowing into your API. Instead of trusting raw @Body() objects, you define exactly what fields are expected and what rules they must satisfy.</p><h3>What is a Pipe?</h3><p>Pipes operate on the arguments of a controller method before the method is invoked. They have two primary uses: validation (throw if invalid) and transformation (convert types).</p><p>Built-in PipePurposeValidationPipeValidates incoming data against a DTO using class-validatorParseIntPipeConverts string route param to integerParseUUIDPipeValidates that a param is a valid UUIDParseEnumPipeValidates value is a member of an enumDefaultValuePipeProvides a default when value is undefined</p><h3>Pipe Binding Levels</h3><pre>// Global — applied to every route<br>app.useGlobalPipes(new ValidationPipe({ whitelist: true }));</pre><pre>// Controller — applied to all routes in the controller<br>@UsePipes(new ValidationPipe())<br>@Controller(&#39;tasks&#39;)</pre><pre>// Method — applied to one route<br>@Post()<br>@UsePipes(new ValidationPipe())</pre><pre>// Parameter — applied to one argument<br>@Param(&#39;id&#39;, ParseUUIDPipe) id: string</pre><p><strong>💻 Hands-On — Validate DevTask Inputs</strong></p><p>1</p><p>Install validation dependencies</p><pre>npm install class-validator class-transformer</pre><p>2</p><p>Create CreateTaskDto src/tasks/dto/create-task.dto.ts</p><pre>import { IsString, IsNotEmpty, MinLength, MaxLength, IsOptional } from &#39;class-validator&#39;;</pre><pre>export class CreateTaskDto {<br>  @IsString()<br>  @IsNotEmpty()<br>  @MinLength(3)<br>  @MaxLength(100)<br>  title: string;</pre><pre>  @IsString()<br>  @IsOptional()<br>  @MaxLength(500)<br>  description?: string;<br>}</pre><p>3</p><p>Create UpdateTaskStatusDto src/tasks/dto/update-task-status.dto.ts</p><pre>import { IsEnum } from &#39;class-validator&#39;;<br>import { TaskStatus } from &#39;../entities/task.entity&#39;;</pre><pre>export class UpdateTaskStatusDto {<br>  @IsEnum(TaskStatus)<br>  status: TaskStatus;<br>}</pre><p>4</p><p>Enable global ValidationPipe in main.ts src/main.ts</p><pre>import { ValidationPipe } from &#39;@nestjs/common&#39;;</pre><pre>async function bootstrap() {<br>  const app = await NestFactory.create(AppModule);<br>  app.useGlobalPipes(<br>    new ValidationPipe({<br>      whitelist: true,        // strip properties not in DTO<br>      forbidNonWhitelisted: true,  // throw if extra properties sent<br>      transform: true,        // auto-transform primitives to their TS types<br>    }),<br>  );<br>  await app.listen(3000);<br>}<br>bootstrap();</pre><p>5</p><p>Update controller to use DTOs</p><pre>@Post()<br>create(@Body() createTaskDto: CreateTaskDto): Task {<br>  return this.tasksService.create(createTaskDto);<br>}</pre><pre>@Patch(&#39;:id/status&#39;)<br>updateStatus(<br>  @Param(&#39;id&#39;, ParseUUIDPipe) id: string,<br>  @Body() dto: UpdateTaskStatusDto,<br>): Task {<br>  return this.tasksService.updateStatus(id, dto.status);<br>}</pre><p>6</p><p>Test validation errors</p><pre># Should fail — title too short<br>curl -X POST http://localhost:3000/tasks \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;CI&quot;}&#39;</pre><pre># Should fail — invalid status<br>curl -X PATCH <a href="http://localhost:3000/tasks/some-id/status">http://localhost:3000/tasks/some-id/status</a> \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;status&quot;:&quot;INVALID_STATUS&quot;}&#39;</pre><pre># Should fail — extra property stripped/rejected<br>curl -X POST <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a> \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;Valid title&quot;,&quot;description&quot;:&quot;desc&quot;,&quot;hacked&quot;:true}&#39;</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>What does whitelist: true on ValidationPipe do?</p><ul><li>Allows only whitelisted IP addresses</li><li>Strips properties from the body that are not in the DTO</li><li>Logs valid requests to a whitelist file</li><li>Disables validation for known-good inputs</li></ul><p>Question 2</p><p>You have @Param(&#39;id&#39;) id: string but want to ensure id is a valid UUID before it reaches your service. What is the cleanest solution?</p><p>Question 3</p><p>Why is transform: true useful when your route param :page is declared as page: number in the method signature?</p><p><strong>🔁 Practice</strong></p><p>Custom Pipe Challenge</p><p>Create a TrimStringPipe that trims whitespace from any string value before it reaches the controller. Apply it globally so that &quot; Write tests &quot; becomes &quot;Write tests&quot; automatically.</p><pre>// Starter scaffold<br>import { PipeTransform, Injectable, ArgumentMetadata } from &#39;@nestjs/common&#39;;</pre><pre>@Injectable()<br>export class TrimStringPipe implements PipeTransform {<br>  transform(value: any, metadata: ArgumentMetadata) {<br>    // Your implementation here<br>  }<br>}</pre><p>6</p><h3>Exception Filters</h3><p>45 min</p><p><strong>📖 Concept</strong></p><h3>Built-in HTTP Exceptions</h3><p>NestJS ships with a set of HttpException subclasses that map to standard HTTP status codes. Throw any of these from a service or controller and the global exception layer converts them to a proper JSON response.</p><p>Exception ClassStatusBadRequestException400UnauthorizedException401ForbiddenException403NotFoundException404ConflictException409UnprocessableEntityException422InternalServerErrorException500</p><h3>Custom Exception Filters</h3><p>When you need a consistent error envelope, custom error codes, or to log errors before responding, implement a custom ExceptionFilter.</p><p><strong>💻 Hands-On — Custom HTTP Exception Filter</strong></p><p>1</p><p>Create the filter src/common/filters/http-exception.filter.ts</p><pre>import {<br>  ExceptionFilter, Catch, ArgumentsHost,<br>  HttpException, HttpStatus, Logger,<br>} from &#39;@nestjs/common&#39;;<br>import { Request, Response } from &#39;express&#39;;</pre><pre>@Catch(HttpException)<br>export class HttpExceptionFilter implements ExceptionFilter {<br>  private readonly logger = new Logger(HttpExceptionFilter.name);</pre><pre>  catch(exception: HttpException, host: ArgumentsHost) {<br>    const ctx = host.switchToHttp();<br>    const response = ctx.getResponse&lt;Response&gt;();<br>    const request = ctx.getRequest&lt;Request&gt;();<br>    const status = exception.getStatus();<br>    const exceptionResponse = exception.getResponse();</pre><pre>    const errorBody = {<br>      statusCode: status,<br>      timestamp: new Date().toISOString(),<br>      path: request.url,<br>      method: request.method,<br>      message:<br>        typeof exceptionResponse === &#39;string&#39;<br>          ? exceptionResponse<br>          : (exceptionResponse as any).message,<br>    };</pre><pre>    this.logger.warn(`[${request.method}] ${request.url} → ${status}`);<br>    response.status(status).json(errorBody);<br>  }<br>}</pre><p>2</p><p>Register globally in main.ts</p><pre>app.useGlobalFilters(new HttpExceptionFilter());</pre><p>3</p><p>Test error responses</p><pre># Should return structured error with timestamp and path<br>curl http://localhost:3000/tasks/non-existent-id</pre><p>You should now see a consistent JSON envelope:</p><pre>{<br>  &quot;statusCode&quot;: 404,<br>  &quot;timestamp&quot;: &quot;2026-05-06T14:23:11.000Z&quot;,<br>  &quot;path&quot;: &quot;/tasks/non-existent-id&quot;,<br>  &quot;method&quot;: &quot;GET&quot;,<br>  &quot;message&quot;: &quot;Task with ID \&quot;non-existent-id\&quot; not found&quot;<br>}</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>An unhandled TypeError: Cannot read properties of undefined is thrown in a service. Which filter catches it?</p><ul><li>Your @Catch(HttpException) filter</li><li>NestJS built-in global exception filter</li><li>No filter — the process crashes</li><li>ValidationPipe</li></ul><p>Question 2</p><p>How do you create a domain-specific exception that always returns 409 Conflict?</p><p>☕ Afternoon Break — 15 minutes</p><p>7</p><h3>Guards</h3><p>45 min</p><p><strong>📖 Concept</strong></p><h3>What is a Guard?</h3><p>Guards implement the CanActivate interface. They run after middleware but before interceptors and pipes. A guard returns true (proceed) or false / throws an exception (reject with 403).</p><p>Guards are the right place for authorization logic — authentication (who are you?) is typically middleware, but authorization (are you allowed to do this?) is a guard.</p><h3>ExecutionContext</h3><p>Guards receive an ExecutionContext that lets you inspect the request, extract metadata, and adapt to different transport layers (HTTP, WebSockets, gRPC).</p><pre>const request = context.switchToHttp().getRequest();<br>const handler = context.getHandler();       // the route method<br>const classRef = context.getClass();        // the controller class<br>// Use Reflector to read custom metadata on the handler or class</pre><h3>Reflector &amp; Custom Metadata</h3><p>Combine guards with @SetMetadata() to create role-based access control:</p><pre>// Define a decorator<br>export const Roles = (...roles: string[]) =&gt; SetMetadata(&#39;roles&#39;, roles);</pre><pre>// Use it on a route<br>@Roles(&#39;admin&#39;)<br>@Delete(&#39;:id&#39;)<br>remove(@Param(&#39;id&#39;) id: string) { ... }</pre><pre>// Read it in a guard<br>const requiredRoles = this.reflector.get&lt;string[]&gt;(&#39;roles&#39;, context.getHandler());</pre><p><strong>💻 Hands-On — API Key Guard</strong></p><p>1</p><p>Create the guard src/common/guards/api-key.guard.ts</p><pre>import {<br>  CanActivate, ExecutionContext, Injectable, UnauthorizedException,<br>} from &#39;@nestjs/common&#39;;</pre><pre>@Injectable()<br>export class ApiKeyGuard implements CanActivate {<br>  private readonly validKey = &#39;devtask-secret-key-2026&#39;; // in real apps: ConfigService</pre><pre>  canActivate(context: ExecutionContext): boolean {<br>    const request = context.switchToHttp().getRequest();<br>    const apiKey = request.headers[&#39;x-api-key&#39;];</pre><pre>    if (!apiKey || apiKey !== this.validKey) {<br>      throw new UnauthorizedException(&#39;Invalid or missing API key&#39;);<br>    }<br>    return true;<br>  }<br>}</pre><p>2</p><p>Apply guard to the TasksController</p><pre>import { UseGuards } from &#39;@nestjs/common&#39;;<br>import { ApiKeyGuard } from &#39;../common/guards/api-key.guard&#39;;</pre><pre>@Controller(&#39;tasks&#39;)<br>@UseGuards(ApiKeyGuard)   // protects all routes in this controller<br>export class TasksController { ... }</pre><p>3</p><p>Test with and without the header</p><pre># Should fail — 401<br>curl http://localhost:3000/tasks</pre><pre># Should succeed — 200<br>curl <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a> \<br>  -H &quot;x-api-key: devtask-secret-key-2026&quot;</pre><pre># POST with key<br>curl -X POST <a href="http://localhost:3000/tasks">http://localhost:3000/tasks</a> \<br>  -H &quot;Content-Type: application/json&quot; \<br>  -H &quot;x-api-key: devtask-secret-key-2026&quot; \<br>  -d &#39;{&quot;title&quot;:&quot;Implement auth guard&quot;,&quot;description&quot;:&quot;Done!&quot;}&#39;</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>You apply @UseGuards(ApiKeyGuard) at the controller level but want one specific route to be public. What is the cleanest approach?</p><p>Question 2</p><p>What is the difference between returning false and throwing UnauthorizedException in a guard?</p><p><strong>🔁 Practice</strong></p><p>Role-Based Guard</p><p>Extend the guard concept: create a RolesGuard that reads a @Roles(&#39;admin&#39;) decorator from the route. The DELETE /tasks/:id route should only be accessible to admins. Pass the role in a custom header x-user-role.</p><p>8</p><h3>Interceptors &amp; Middleware</h3><p>45 min</p><p><strong>📖 Concept</strong></p><h3>What is an Interceptor?</h3><p>Interceptors wrap the request/response cycle using RxJS Observables. They can:</p><ul><li>Run logic before the route handler (e.g., start a timer)</li><li>Modify or replace the response (e.g., wrap in a standard envelope)</li><li>Handle exceptions from the route</li><li>Cache responses</li></ul><pre>@Injectable()<br>export class MyInterceptor implements NestInterceptor {<br>  intercept(context: ExecutionContext, next: CallHandler): Observable&lt;any&gt; {<br>    // Runs BEFORE the handler<br>    return next<br>      .handle()         // calls the route handler<br>      .pipe(<br>        map(data =&gt; ({ success: true, data })),  // transforms the response<br>        tap(() =&gt; /* runs after handler, logs etc */),<br>      );<br>  }<br>}</pre><h3>Middleware vs Interceptors vs Guards</h3><p>FeatureMiddlewareGuardInterceptorRuns before handler✅✅✅Access to response✅❌✅Can modify response❌❌✅Can abort request✅✅✅NestJS DI support✅✅✅Typical useLogging, CORS, body-parseAuth, rolesLogging, caching, transform</p><p><strong>💻 Hands-On — Logging Interceptor &amp; Response Transform</strong></p><p>1</p><p>Create a logging interceptor src/common/interceptors/logging.interceptor.ts</p><pre>import {<br>  Injectable, NestInterceptor, ExecutionContext,<br>  CallHandler, Logger,<br>} from &#39;@nestjs/common&#39;;<br>import { Observable } from &#39;rxjs&#39;;<br>import { tap } from &#39;rxjs/operators&#39;;</pre><pre>@Injectable()<br>export class LoggingInterceptor implements NestInterceptor {<br>  private readonly logger = new Logger(&#39;HTTP&#39;);</pre><pre>  intercept(context: ExecutionContext, next: CallHandler): Observable&lt;any&gt; {<br>    const req = context.switchToHttp().getRequest();<br>    const { method, url } = req;<br>    const start = Date.now();</pre><pre>    return next.handle().pipe(<br>      tap(() =&gt; {<br>        const ms = Date.now() - start;<br>        this.logger.log(`${method} ${url} — ${ms}ms`);<br>      }),<br>    );<br>  }<br>}</pre><p>2</p><p>Create a response transform interceptor src/common/interceptors/transform.interceptor.ts</p><pre>import {<br>  Injectable, NestInterceptor, ExecutionContext, CallHandler,<br>} from &#39;@nestjs/common&#39;;<br>import { Observable } from &#39;rxjs&#39;;<br>import { map } from &#39;rxjs/operators&#39;;</pre><pre>export interface ApiResponse&lt;T&gt; {<br>  success: boolean;<br>  data: T;<br>  timestamp: string;<br>}</pre><pre>@Injectable()<br>export class TransformInterceptor&lt;T&gt;<br>  implements NestInterceptor&lt;T, ApiResponse&lt;T&gt;&gt; {<br>  intercept(<br>    context: ExecutionContext,<br>    next: CallHandler,<br>  ): Observable&lt;ApiResponse&lt;T&gt;&gt; {<br>    return next.handle().pipe(<br>      map((data) =&gt; ({<br>        success: true,<br>        data,<br>        timestamp: new Date().toISOString(),<br>      })),<br>    );<br>  }<br>}</pre><p>3</p><p>Register both globally src/main.ts</p><pre>app.useGlobalInterceptors(<br>  new LoggingInterceptor(),<br>  new TransformInterceptor(),<br>);</pre><p>4</p><p>Test the response envelope</p><pre>curl http://localhost:3000/tasks -H &quot;x-api-key: devtask-secret-key-2026&quot;</pre><p>All responses are now wrapped:</p><pre>{<br>  &quot;success&quot;: true,<br>  &quot;data&quot;: [...],<br>  &quot;timestamp&quot;: &quot;2026-05-06T15:10:00.000Z&quot;<br>}</pre><p><strong>❓ Quiz</strong></p><p>Question 1</p><p>Your TransformInterceptor wraps all responses in { success: true, data: ... }. But your HttpExceptionFilter returns { statusCode, message, ... } directly. Will exceptions be double-wrapped?</p><p>Question 2</p><p>You want to add a Cache-Control: max-age=60 header to GET /tasks responses only. Should you use middleware or an interceptor, and why?</p><p><strong>🔁 Practice</strong></p><p>Timeout Interceptor</p><p>Implement a TimeoutInterceptor that cancels any request taking longer than 5 seconds and throws a RequestTimeoutException. Hint: use RxJS timeout operator and catch the TimeoutError.</p><pre>import { timeout, catchError } from &#39;rxjs/operators&#39;;<br>import { TimeoutError, throwError } from &#39;rxjs&#39;;<br>import { RequestTimeoutException } from &#39;@nestjs/common&#39;;</pre><pre>// In your intercept method:<br>return next.handle().pipe(<br>  timeout(5000),<br>  catchError((err) =&gt; {<br>    if (err instanceof TimeoutError) {<br>      return throwError(() =&gt; new RequestTimeoutException());<br>    }<br>    return throwError(() =&gt; err);<br>  }),<br>);</pre><p>🏆</p><h3>Final Challenge — Complete the DevTask API</h3><p>30 min</p><p>You have all the building blocks. Complete the DevTask API by combining everything you’ve learned:</p><p>Challenge 1 — Task Assignment</p><p>Add an assignedTo field to tasks. When creating a task, validate the username exists in UsersService. Throw a BadRequestException if the username doesn&#39;t exist.</p><p>Challenge 2 — Config-driven API Key</p><p>Move the API key from a hardcoded string to an environment variable using NestJS ConfigModule. Install @nestjs/config and inject ConfigService into your guard.</p><p>Challenge 3 — Pagination</p><p>Add ?page=1&amp;limit=10 support to GET /tasks. Create a PaginationDto with @IsOptional(), @IsInt(), @Min(1), and @Max(100) decorators. Return paginated results with total, page, limit, and data fields.</p><p>Challenge 4 — Audit Interceptor</p><p>Create an AuditInterceptor that logs every POST, PATCH, and DELETE request to an in-memory audit log with: timestamp, method, url, and apiKey (from request header). Expose GET /audit to retrieve the audit log (admin only).</p><h3>📚 Quick Reference — NestJS CLI Commands</h3><pre>nest new &lt;app&gt;                   # scaffold new project<br>nest generate module &lt;name&gt;      # feature module<br>nest generate controller &lt;name&gt;  # controller (+ spec)<br>nest generate service &lt;name&gt;     # service (+ spec)<br>nest generate guard &lt;name&gt;       # guard<br>nest generate interceptor &lt;name&gt; # interceptor<br>nest generate pipe &lt;name&gt;        # pipe<br>nest generate filter &lt;name&gt;      # exception filter<br>nest build                       # compile TypeScript<br>nest start:dev                   # watch mode with hot reload</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d994cf89fd1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Blockchain Development Learning Path for Fullstack Developers]]></title>
            <link>https://medium.com/@maheshhasantha/blockchain-development-learning-path-for-fullstack-developers-0c7ccf1d2e1e?source=rss-1576ad9fb1ea------2</link>
            <guid isPermaLink="false">https://medium.com/p/0c7ccf1d2e1e</guid>
            <dc:creator><![CDATA[Mahesh Kandegedara]]></dc:creator>
            <pubDate>Thu, 02 Oct 2025 11:05:30 GMT</pubDate>
            <atom:updated>2025-10-02T11:05:30.731Z</atom:updated>
            <content:encoded><![CDATA[<h3>Course Overview</h3><p><strong>Target Audience:</strong> Fresh graduates with fullstack development experience<br> <strong>Duration:</strong> 6 weeks structured + self-paced Cosmos development<br> <strong>Goal:</strong> Build foundational blockchain knowledge and specialize in Cosmos ecosystem</p><h3>Phase 1: Blockchain Fundamentals (Week 1–2)</h3><h3>Learning Objectives</h3><ul><li>Understand distributed ledger technology and consensus mechanisms</li><li>Grasp cryptographic principles underlying blockchain</li><li>Explore major blockchain ecosystems and their use cases</li></ul><h3>Core Topics</h3><p><strong>Week 1: Introduction to Blockchain</strong></p><ul><li>What is blockchain and how it differs from traditional databases</li><li>Hash functions, public-key cryptography, and digital signatures</li><li>Consensus mechanisms (PoW, PoS, BFT)</li><li>Blockchain trilemma: scalability, security, decentralization</li></ul><p><strong>Week 2: Major Ecosystems Overview</strong></p><ul><li>Bitcoin: The first blockchain and digital currency</li><li>Ethereum: Smart contract platform and EVM</li><li>Alternative Layer 1s: Solana, Avalanche, Polkadot</li><li>Layer 2 solutions: Optimism, Arbitrum, zkSync</li></ul><h3>Resources</h3><p><strong>Foundational Materials:</strong></p><ul><li><a href="https://www.coursera.org/learn/blockchain-basics">Blockchain Basics — Coursera IBM</a> — Free introductory course</li><li><a href="https://bitcoin.org/bitcoin.pdf">Bitcoin Whitepaper</a> — Essential reading</li><li><a href="https://ethereum.org/en/learn/">Ethereum.org Learn Hub</a> — Comprehensive Ethereum intro</li><li><a href="https://www.youtube.com/watch?v=bBC-nXj3Ng4">But How Does Bitcoin Actually Work? — 3Blue1Brown</a> — Visual explanation</li></ul><p><strong>Interactive Learning:</strong></p><ul><li><a href="https://andersbrownworth.com/blockchain/">Blockchain Demo</a> — Visual blockchain simulator</li><li><a href="https://cryptozombies.io/">CryptoZombies</a> — Learn Solidity through gamification</li></ul><p><strong>Reading:</strong></p><ul><li><em>Mastering Bitcoin</em> by Andreas Antonopoulos (Chapters 1–4)</li><li><a href="https://a16z.com/crypto-canon/">A16z Crypto Canon</a> — Curated reading list</li></ul><h3>Phase 2: Transactions &amp; Smart Contracts (Week 3–4)</h3><h3>Learning Objectives</h3><ul><li>Understand transaction lifecycle and block formation</li><li>Write and deploy basic smart contracts</li><li>Grasp token standards and common contract patterns</li></ul><h3>Core Topics</h3><p><strong>Week 3: Transactions Deep Dive</strong></p><ul><li>UTXO vs Account model</li><li>Transaction structure and signing</li><li>Gas fees and transaction optimization</li><li>Mempool and transaction finality</li><li>Wallet architecture and key management</li></ul><p><strong>Week 4: Smart Contracts</strong></p><ul><li>Introduction to Solidity and smart contract development</li><li>Contract deployment and interaction</li><li>Token standards (ERC-20, ERC-721, ERC-1155)</li><li>Smart contract security considerations and common vulnerabilities</li><li>Testing and debugging smart contracts</li></ul><h3>Resources</h3><p><strong>Smart Contract Development:</strong></p><ul><li><a href="https://docs.soliditylang.org/">Solidity Documentation</a> — Official docs</li><li><a href="https://remix.ethereum.org/">Remix IDE</a> — Browser-based development environment</li><li><a href="https://docs.openzeppelin.com/contracts/">OpenZeppelin Contracts</a> — Secure contract templates</li><li><a href="https://ethernaut.openzeppelin.com/">Ethernaut</a> — Security-focused challenges</li></ul><p><strong>Video Courses:</strong></p><ul><li><a href="https://chain.link/bootcamp">Chainlink Developer Bootcamp 2024</a> — Comprehensive smart contract course</li><li><a href="https://www.youtube.com/watch?v=umepbfKp5rI">Patrick Collins — Smart Contract Course</a> — 32-hour comprehensive tutorial</li></ul><p><strong>Upcoming Training:</strong></p><ul><li><a href="https://email.chain.link/e3t/Ctc/W3+113/d2rQJ-04/VWzLc82N9W6sW5s-Yqd9gzd6yW8mS6hr5nfJ6KN6wcHqF3qg1qW7lCdLW6lZ3pVW2LS_x81RWVYSW3z9b6G6XtJzZW4j2Zbv1vj8xDW46ccPb295-pZW7tG_d27y4twkW8bw61F7k7PQrW2T08137K-5JHW7rMZC-1jm1KxW2cJg5Q511zwLW99W2Pq4rlQmFN79FKj8-8tMHN7hzXmnwm1tyW6q3szf5hYW3lW7NG_hn43Mm93VNdTL03Py_YMW20D1gp1SD0BCW15qpGw83ZnS5N3w0F85YKQBQW7v1P502-ZSl4W2V-9F92b3qGpW8wXPTG80g81nW2TB_Rf4rzRnFW86tGZw65z1MkW5rJgvB4KgD1-f7zPM9b04"><strong>Chainlink Developer Expert Program</strong></a> — Advanced oracle integration and cross-chain development</li></ul><p><strong>Practice Projects:</strong></p><ul><li>Build an ERC-20 token</li><li>Create a simple NFT marketplace</li><li>Implement a multi-signature wallet</li></ul><h3>Phase 3: Introduction to Cosmos Ecosystem (Week 5–6)</h3><h3>Learning Objectives</h3><ul><li>Understand the Cosmos vision of interoperability</li><li>Learn Tendermint consensus and IBC protocol</li><li>Explore application-specific blockchains vs smart contracts</li></ul><h3>Core Topics</h3><p><strong>Week 5: Cosmos Architecture</strong></p><ul><li>The Cosmos Hub and the Internet of Blockchains vision</li><li>Tendermint Core: Byzantine Fault Tolerant consensus</li><li>Cosmos SDK: Modular blockchain framework</li><li>IBC (Inter-Blockchain Communication) protocol</li><li>Differences from Ethereum and other monolithic chains</li></ul><p><strong>Week 6: Major Cosmos Chains</strong></p><ul><li><strong>Cosmos Hub (ATOM)</strong>: The first hub and governance</li><li><strong>Osmosis</strong>: DEX-focused chain with superfluid staking</li><li><strong>Neutron</strong>: Smart contract platform with cross-chain queries</li><li><strong>Injective, Celestia, dYdX v4</strong>: Specialized appchains</li><li>Shared security and interchain security</li></ul><h3>Why Cosmos is Different</h3><p><strong>Key Differentiators:</strong></p><ol><li><strong>Sovereignty</strong>: Each chain has its own governance and validator set</li><li><strong>Scalability</strong>: Horizontal scaling through multiple chains vs vertical scaling</li><li><strong>Interoperability</strong>: Native cross-chain communication via IBC</li><li><strong>Customization</strong>: Build application-specific chains optimized for your use case</li><li><strong>Developer Experience</strong>: CosmWasm for smart contracts (Rust), Cosmos SDK for appchains (Go)</li></ol><p><strong>Comparison Table:</strong></p><pre>FeatureEthereumCosmosPolkadotArchitectureMonolithicModularModularConsensusPoS (Gasper)Tendermint BFTGRANDPA/BABEScalabilityLayer 2sMultiple chainsParachainsInteropBridgesIBC nativeXCMPDev LanguageSolidityGo/RustRust</pre><h3>Resources</h3><p><strong>Cosmos Fundamentals:</strong></p><ul><li><a href="https://ida.interchain.io/academy/2-cosmos-concepts/"><strong>Interchain Developer Academy</strong></a> — Primary learning resource</li><li>Start with “What is Cosmos?” module</li><li>Progress through “Blockchain Technology” section</li><li>Focus on “Cosmos Concepts” and “IBC” modules</li><li><a href="https://docs.cosmos.network/">Cosmos Network Documentation</a> — Official docs</li><li><a href="https://tutorials.cosmos.network/">Cosmos SDK Tutorials</a> — Hands-on guides</li></ul><p><strong>Video Content:</strong></p><ul><li><a href="https://www.youtube.com/watch?v=v3fJQjLgKj8">Cosmos Explained — Whiteboard Crypto</a> — Beginner-friendly overview</li><li><a href="https://www.youtube.com/playlist?list=PLdQIb0qr3pnBbG5ZG-0gr3zM86_s8Rpqv">Cosmos SDK Tutorial Series</a> — Official Cosmos tutorials</li></ul><p><strong>Chain-Specific Resources:</strong></p><ul><li><a href="https://docs.osmosis.zone/">Osmosis Documentation</a> — Learn about DEX-specific features</li><li><a href="https://docs.neutron.org/">Neutron Docs</a> — CosmWasm and cross-chain queries</li><li><a href="https://forum.cosmos.network/">Cosmos Hub Forum</a> — Governance discussions</li></ul><p><strong>IBC Deep Dive:</strong></p><ul><li><a href="https://ibc.cosmos.network/">IBC Protocol Documentation</a> — Technical specification</li><li><a href="https://mapofzones.com/">Map of Zones</a> — Visualize IBC connections</li><li><a href="https://www.ibcgang.dev/">IBC Gang Podcast</a> — Weekly ecosystem updates</li></ul><h3>Phase 4: Self-Paced Cosmos Development (Following Interchain Academy)</h3><h3>Overview</h3><p>After completing the foundational 6 weeks, you’ll transition to self-paced learning using the comprehensive Interchain Developer Academy curriculum. This allows you to progress at your own speed while building practical skills.</p><h3>Learning Path Structure</h3><p>Follow the <a href="https://ida.interchain.io/"><strong>Interchain Developer Academy</strong></a> curriculum in this sequence:</p><h4>Module 1: Cosmos SDK Fundamentals</h4><p><strong>Academy Path:</strong> <a href="https://ida.interchain.io/academy/2-cosmos-concepts/">Introduction to Cosmos SDK</a></p><p><strong>Topics Covered:</strong></p><ul><li>Main concepts of Cosmos SDK</li><li>Architecture of a Cosmos blockchain</li><li>Accounts, transactions, and messages</li><li>Modules and their interactions</li><li>BaseApp and ABCI (Application Blockchain Interface)</li></ul><p><strong>Hands-On Activities:</strong></p><ul><li>Set up your development environment</li><li>Run a local node</li><li>Interact with a blockchain using CLI</li><li>Explore the anatomy of a transaction</li></ul><p><strong>Time Estimate:</strong> 2–3 weeks</p><h4>Module 2: Building Your First Blockchain</h4><p><strong>Academy Path:</strong> <a href="https://ida.interchain.io/academy/3-my-own-chain/">Run Your Own Cosmos Chain</a></p><p><strong>Topics Covered:</strong></p><ul><li>Ignite CLI for rapid development</li><li>Creating custom modules</li><li>Defining messages and queries</li><li>Implementing keepers (state management)</li><li>Genesis configuration and chain initialization</li></ul><p><strong>Hands-On Activities:</strong></p><ul><li>Build a checkers game blockchain (Academy tutorial)</li><li>Create custom message types</li><li>Implement game logic in keepers</li><li>Test your chain locally</li></ul><p><strong>Time Estimate:</strong> 3–4 weeks</p><h4>Module 3: IBC and Cross-Chain Communication</h4><p><strong>Academy Path:</strong> <a href="https://ida.interchain.io/academy/3-ibc/">Inter-Blockchain Communication</a></p><p><strong>Topics Covered:</strong></p><ul><li>IBC protocol architecture</li><li>Channels, connections, and clients</li><li>Token transfers between chains</li><li>Relayers and how they work</li><li>IBC middleware</li></ul><p><strong>Hands-On Activities:</strong></p><ul><li>Enable IBC on your custom chain</li><li>Perform cross-chain token transfers</li><li>Set up and run a relayer</li><li>Build an IBC-enabled application</li></ul><p><strong>Time Estimate:</strong> 2–3 weeks</p><h4>Module 4: CosmWasm Smart Contracts</h4><p><strong>Academy Path:</strong> <a href="https://ida.interchain.io/academy/4-cosmwasm/">Introduction to CosmWasm</a></p><p><strong>Topics Covered:</strong></p><ul><li>Rust basics for blockchain</li><li>CosmWasm contract structure</li><li>Contract instantiation, execution, and queries</li><li>State management in CosmWasm</li><li>Testing CosmWasm contracts</li></ul><p><strong>Hands-On Activities:</strong></p><ul><li>Write your first CosmWasm contract</li><li>Deploy to a testnet (Neutron or Juno)</li><li>Build a token contract</li><li>Implement contract-to-contract calls</li></ul><p><strong>Time Estimate:</strong> 3–4 weeks</p><h4>Module 5: Advanced Topics (Optional)</h4><p><strong>Academy Path:</strong> <a href="https://ida.interchain.io/academy/5-run-in-prod/">Advanced Cosmos SDK</a></p><p><strong>Topics Covered:</strong></p><ul><li>Running nodes in production</li><li>Chain upgrades and governance</li><li>Performance optimization</li><li>Security best practices</li><li>Monitoring and observability</li></ul><p><strong>Hands-On Activities:</strong></p><ul><li>Set up a production-grade node</li><li>Implement a chain upgrade</li><li>Configure monitoring tools</li><li>Participate in testnet governance</li></ul><p><strong>Time Estimate:</strong> 2–3 weeks</p><h3>Self-Paced Learning Tips</h3><p><strong>Stay Organized:</strong></p><ul><li>Set weekly goals and track your progress</li><li>Complete all hands-on exercises in each module</li><li>Take notes and document your learning</li><li>Build a portfolio of projects</li></ul><p><strong>Engage with the Community:</strong></p><ul><li>Join <a href="https://discord.gg/cosmosnetwork">Cosmos Discord</a> for questions</li><li>Participate in <a href="https://cosmos.network/community">Cosmos Developer Calls</a></li><li>Follow <a href="https://blog.cosmos.network/">Cosmos Blog</a> for updates</li><li>Connect with other learners in study groups</li></ul><p><strong>Practice Consistently:</strong></p><ul><li>Code daily, even if just for 30 minutes</li><li>Build small projects after each module</li><li>Contribute to open-source Cosmos projects</li><li>Participate in hackathons and bounties</li></ul><p><strong>Track Your Progress:</strong></p><ul><li>Complete the Academy quizzes and assessments</li><li>Build a capstone project combining multiple concepts</li><li>Document your journey on GitHub or a blog</li><li>Create a portfolio showcasing your Cosmos skills</li></ul><h3>Recommended Project Milestones</h3><p><strong>After SDK Fundamentals:</strong></p><ul><li>Build a simple governance module</li><li>Create a custom token with unique features</li><li>Implement a basic staking system</li></ul><p><strong>After Building Your First Blockchain:</strong></p><ul><li>Launch a testnet for your custom chain</li><li>Add multiple custom modules</li><li>Implement complex state transitions</li></ul><p><strong>After IBC Module:</strong></p><ul><li>Build a cross-chain application</li><li>Create an IBC-enabled NFT that can move between chains</li><li>Implement a cross-chain oracle</li></ul><p><strong>After CosmWasm:</strong></p><ul><li>Deploy a DApp with smart contracts on Neutron</li><li>Build a DAO using CosmWasm</li><li>Create an interchain smart contract system</li></ul><p><strong>Capstone Project Ideas:</strong></p><ol><li>Cross-chain decentralized marketplace</li><li>Interchain identity and authentication system</li><li>Multi-chain asset management platform</li><li>Cosmos-based social network with tokens</li><li>Supply chain tracking using multiple appchains</li></ol><h3>Development Tools &amp; Environment Setup</h3><h3>Essential Tools</h3><p><strong>Blockchain Development:</strong></p><ul><li><a href="https://ignite.com/">Ignite CLI</a> — Scaffold Cosmos chains quickly</li><li><a href="https://github.com/cosmos/cosmjs">CosmJS</a> — JavaScript library for Cosmos</li><li><a href="https://www.rust-lang.org/">Rust</a> — For CosmWasm development</li><li><a href="https://golang.org/">Go</a> — For Cosmos SDK development</li></ul><p><strong>IDEs and Extensions:</strong></p><ul><li><a href="https://code.visualstudio.com/">VS Code</a> with Rust Analyzer and Go extensions</li><li><a href="https://ide.cosmwasm.com/">CosmWasm IDE</a> — Browser-based development</li><li><a href="https://www.keplr.app/">Keplr Wallet</a> — Essential for testing</li></ul><p><strong>Testing and Deployment:</strong></p><ul><li><a href="https://docs.osmosis.zone/networks/join-mainnet/">LocalOsmosis</a> — Local testnet</li><li><a href="https://docs.cosmos.network/main/tooling/faucets">Testnet Faucets</a> — Get test tokens</li><li><a href="https://hermes.informal.systems/">Hermes Relayer</a> — IBC relaying</li></ul><h3>Setting Up Your Environment</h3><p><strong>Step 1: Install Prerequisites</strong></p><p>bash</p><pre># Install Go<br># Visit https://golang.org/doc/install</pre><pre># Install Rust<br>curl --proto &#39;=https&#39; --tlsv1.2 -sSf <a href="https://sh.rustup.rs/">https://sh.rustup.rs</a> | sh</pre><pre># Install Ignite CLI<br>curl <a href="https://get.ignite.com/cli!">https://get.ignite.com/cli!</a> | bash</pre><p><strong>Step 2: Clone Academy Resources</strong></p><p>bash</p><pre># Clone the Interchain Academy examples<br>git clone https://github.com/cosmos/sdk-tutorials</pre><pre># Follow the setup instructions in each tutorial</pre><p><strong>Step 3: Set Up Testnet Access</strong></p><ul><li>Create a Keplr wallet</li><li>Request testnet tokens from faucets</li><li>Connect to public testnets (Theta, Sandbar)</li></ul><h3>Additional Resources for Self-Paced Learning</h3><h3>Documentation &amp; References</h3><ul><li><a href="https://docs.cosmos.network/main">Cosmos SDK Documentation</a> — Complete technical reference</li><li><a href="https://docs.cosmwasm.com/">CosmWasm Documentation</a> — Smart contract development</li><li><a href="https://ibc.cosmos.network/">IBC Documentation</a> — Cross-chain protocol</li><li><a href="https://docs.tendermint.com/">Tendermint Core Docs</a> — Consensus engine</li></ul><h3>Video Tutorials</h3><ul><li><a href="https://www.youtube.com/c/CosmosProject">Cosmos SDK Workshop</a> — Official channel</li><li><a href="https://www.youtube.com/@interchain_io">Interchain.io YouTube</a> — Deep dives</li><li><a href="https://www.youtube.com/watch?v=VTjiC4wcd7c">CosmWasm Zero to Hero</a> — Contract development</li></ul><h3>Community Learning</h3><ul><li><a href="https://forum.cosmos.network/">Cosmos Forum</a> — Technical discussions</li><li><a href="https://area51.stackexchange.com/proposals/126626/cosmos">Cosmos Stack Exchange</a> — Q&amp;A</li><li><a href="https://www.reddit.com/r/cosmosnetwork/">Cosmos Reddit</a> — General community</li></ul><h3>Practice Platforms</h3><ul><li><a href="https://learn.questbook.xyz/">Questbook Cosmos Course</a> — Earn while learning</li><li><a href="https://dacade.org/">Dacade Cosmos Track</a> — Project-based learning</li><li><a href="https://cosmosdevs.com/">Cosmos Bounties</a> — Real-world tasks</li></ul><h3>Hackathons &amp; Events</h3><ul><li><a href="https://hackatom.org/">HackAtom</a> — Annual Cosmos hackathon</li><li><a href="https://cosmoverse.org/">Cosmoverse</a> — Annual conference</li><li><a href="https://www.meetup.com/topics/cosmos/">Local Cosmos Meetups</a> — Network locally</li></ul><h3>Assessment &amp; Progress Tracking</h3><h3>Module Completion Checklist</h3><p><strong>Cosmos SDK Fundamentals:</strong></p><ul><li>☐ Explain Tendermint consensus to a peer</li><li>☐ Successfully run a local node</li><li>☐ Create and submit a transaction via CLI</li><li>☐ Understand the lifecycle of a transaction</li></ul><p><strong>Building Your First Blockchain:</strong></p><ul><li>☐ Build a custom module with Ignite CLI</li><li>☐ Implement at least 3 message types</li><li>☐ Write unit tests for your keepers</li><li>☐ Launch a local testnet</li></ul><p><strong>IBC Module:</strong></p><ul><li>☐ Successfully transfer tokens between chains</li><li>☐ Set up and run a relayer</li><li>☐ Explain IBC handshake process</li><li>☐ Build an IBC-enabled feature</li></ul><p><strong>CosmWasm:</strong></p><ul><li>☐ Deploy a contract to testnet</li><li>☐ Write integration tests</li><li>☐ Implement query and execute messages</li><li>☐ Build a frontend that interacts with your contract</li></ul><h3>Portfolio Development</h3><p><strong>Document Your Journey:</strong></p><ul><li>Create a GitHub repository for each major project</li><li>Write README files with setup instructions</li><li>Include architecture diagrams</li><li>Document challenges and solutions</li></ul><p><strong>Build a Portfolio Site:</strong></p><ul><li>Showcase your Cosmos projects</li><li>Include live demos on testnets</li><li>Write blog posts about your learning</li><li>Link to your contributions</li></ul><p><strong>Get Involved:</strong></p><ul><li>Contribute to Cosmos open-source projects</li><li>Answer questions in community channels</li><li>Write tutorials for others</li><li>Speak at local meetups</li></ul><h3>Career Development &amp; Next Steps</h3><h3>Specialization Paths</h3><p><strong>Cosmos SDK Developer:</strong></p><ul><li>Focus on building custom blockchains</li><li>Deep dive into module development</li><li>Learn chain upgrades and migrations</li><li>Study production deployment</li></ul><p><strong>CosmWasm Engineer:</strong></p><ul><li>Master Rust and smart contract security</li><li>Build complex contract systems</li><li>Explore cross-chain contracts</li><li>Learn contract optimization</li></ul><p><strong>Infrastructure &amp; DevOps:</strong></p><ul><li>Node operation and monitoring</li><li>Validator setup and management</li><li>Network security</li><li>Performance tuning</li></ul><p><strong>Protocol Developer:</strong></p><ul><li>Contribute to Cosmos SDK core</li><li>Work on IBC protocol improvements</li><li>Research consensus mechanisms</li><li>Build developer tools</li></ul><p><strong>Companies in the Ecosystem:</strong></p><ul><li>Informal Systems (IBC and Tendermint)</li><li>Interchain Foundation</li><li>Cosmos Hub contributors</li><li>Osmosis Labs, Neutron, and other chain teams</li><li>Cross-chain infrastructure companies</li></ul><h3>Continuous Learning</h3><p><strong>Stay Current:</strong></p><ul><li>Follow Cosmos GitHub repositories</li><li>Read Cosmos SDK release notes</li><li>Participate in governance discussions</li><li>Attend Cosmos events and conferences</li></ul><p><strong>Advanced Topics to Explore:</strong></p><ul><li>MEV (Maximal Extractable Value) in Cosmos</li><li>Zero-knowledge proofs (Penumbra, Namada)</li><li>Cross-chain DeFi protocols</li><li>Interchain security and shared security</li><li>Threshold cryptography and multi-party computation</li></ul><h3>Final Notes</h3><p>This learning path provides structure for the first 6 weeks and then empowers you to take control of your learning journey through the comprehensive Interchain Academy curriculum. The self-paced approach allows you to:</p><ul><li><strong>Progress at your own speed</strong> — Spend more time on challenging topics</li><li><strong>Build deeper expertise</strong> — Follow your interests within the ecosystem</li><li><strong>Gain practical experience</strong> — Complete hands-on projects at each stage</li><li><strong>Join the community</strong> — Connect with other developers and contributors</li></ul><p><strong>Key Success Factors:</strong></p><ul><li>Complete all hands-on exercises in the Academy</li><li>Build projects that solve real problems</li><li>Engage actively with the community</li><li>Contribute to open-source projects</li><li>Document and share your learning</li></ul><p><strong>Remember:</strong> The Cosmos ecosystem values builders who contribute to the community. Your journey from student to contributor to core developer is supported by comprehensive resources, a welcoming community, and exciting opportunities.</p><p>Start with the fundamentals, progress through the Academy curriculum at your own pace, and build amazing interchain applications! 🚀</p><p><strong>Next Step:</strong> Begin with Phase 1 and schedule your learning time. Set a target date to complete the 6-week structured portion, then dive into the Interchain Academy for self-paced mastery.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0c7ccf1d2e1e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Running Redis Cache container on a Kubernetes Pod]]></title>
            <link>https://medium.com/@maheshhasantha/running-redis-cache-container-on-a-kubernetes-pod-1fbcb995f11e?source=rss-1576ad9fb1ea------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fbcb995f11e</guid>
            <dc:creator><![CDATA[Mahesh Kandegedara]]></dc:creator>
            <pubDate>Sun, 11 Oct 2020 17:36:15 GMT</pubDate>
            <atom:updated>2020-10-11T17:36:15.635Z</atom:updated>
            <content:encoded><![CDATA[<p>Redis can setup in Kubernetes mainly in few different ways</p><ul><li>as a service running on its own pod: other services can communicate with the exposed port</li><li>as a side-car container sharing the pod with dependent service: the service will run on inside the same pod, meaning the Redis DB will reset if the pod is restarted.</li></ul><h3>Running Redis container inside a pod</h3><p>When deploying a Redis instance on a cluster, the most common and easiest way would be using a helm chart from preferably <a href="http://redis.io/">redis.io</a></p><p><a href="https://github.com/helm/charts/tree/master/stable/redis">helm/charts</a></p><p><a href="https://bitnami.com/stack/redis/helm">Redis</a></p><p>But for deploying to Kubernetes, need a deployment config specifying the container specs:</p><pre>- name: master<br>    image: k8s.gcr.io/redis:e2e  # or just image: redis<br>    resources:<br>      requests:<br>         cpu: 500m<br>         memory: 1000Mi<br>      ports:<br>         - containerPort: 6379</pre><h3>Redis Configuration</h3><p>the main config is needed defining the beans to create a redis cache manager and other necessary things like redisTemplates, custom serializations and connection factory. There are many connector libraries available, i used jedis (others reddison, lettuce)</p><pre>        &lt;dependency&gt;<br>            &lt;groupId&gt;org.springframework.boot&lt;/groupId&gt;<br>            &lt;artifactId&gt;spring-boot-starter-data-redis&lt;/artifactId&gt;<br>            &lt;version&gt;2.3.3.RELEASE&lt;/version&gt;<br>        &lt;/dependency&gt;</pre><pre>        &lt;dependency&gt;<br>            &lt;groupId&gt;redis.clients&lt;/groupId&gt;<br>            &lt;artifactId&gt;jedis&lt;/artifactId&gt;<br>            &lt;version&gt;2.9.0&lt;/version&gt;<br>        &lt;/dependency&gt;</pre><pre>@Bean<br>fun jedisConnectionFactory(): JedisConnectionFactory {<br>        val configuration = RedisStandaloneConfiguration(&quot;localhost&quot;, 6379)<br>            if (Objects.nonNull(password) &amp;&amp; password!!.trim { it &lt;= &#39; &#39; } != &quot;&quot;) {<br>            configuration.setPassword(password)<br>        }<br>        val jedisConnectionFactory = JedisConnectionFactory(configuration)<br>        return jedisConnectionFactory<br>}</pre><h3>Cashing json values</h3><p>by default, spring data Redis caches key, value pairs of type String. But when Redis is used to store intermediate backend responses containing custom objects, a custom serializer must be implemented, if the class hierarchy does not implement serializable. Also when de-serializing kotlin objects some errors can be avoided by registering KotlinModule() to the mapper on initializing the jackson serializer.</p><pre>@Bean(name = [&quot;redisCMJson&quot;])<br>fun redisCacheManager():RedisCacheManager {<br>  val stringSerializer = StringRedisSerializer()<br>  val mapper = ObjectMapper()<br>                .registerModule(KotlinModule())<br>  mapper.enableDefaultTyping(DefaultTyping.NON_FINAL, As.PROPERTY)<br>  val jacksonSerializer: RedisSerializer&lt;Any&gt; = GenericJackson2JsonRedisSerializer(mapper)<br>        return RedisCacheManager(RedisCacheWriter.nonLockingRedisCacheWriter(jedisConnectionFactory()),RedisCacheConfiguration.defaultCacheConfig()<br>.serializeKeysWith(SerializationPair.fromSerializer(stringSerializer))                       .serializeValuesWith(SerializationPair.fromSerializer&lt;Any&gt;(jacksonSerializer)))<br>    }</pre><h3>Cashing responses with Spring @Casheable</h3><pre>@Cacheable(value = &quot;posts&quot;, key = &quot;#unique key&quot;, unless = &quot;#result == null&quot;, cacheManager = &quot;redisCMJson&quot;)</pre><p>and @EnableCaching at the main class</p><h3>Cash eviction</h3><pre>@CacheEvict(value = &quot;posts&quot;, key=&quot;#key&quot;)</pre><p>Useful links:</p><ul><li><a href="https://medium.com/@ArcanjoQueiroz/using-spring-boot-data-redis-for-caching-purposes-in-your-application-4da091ae369c">Using Spring-Boot Data Redis for caching purposes in your application</a></li><li><a href="https://cloud.google.com/blog/products/databases/running-redis-on-gcp-four-deployment-scenarios">Running Redis on GCP: four deployment scenarios | Google Cloud Blog</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fbcb995f11e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cryptocurrency as a Disruptive Technology for Businesses]]></title>
            <link>https://medium.com/@maheshhasantha/cryptocurrency-as-a-disruptive-technology-for-businesses-680e72c2f8f6?source=rss-1576ad9fb1ea------2</link>
            <guid isPermaLink="false">https://medium.com/p/680e72c2f8f6</guid>
            <dc:creator><![CDATA[Mahesh Kandegedara]]></dc:creator>
            <pubDate>Sat, 05 Sep 2020 18:14:08 GMT</pubDate>
            <atom:updated>2020-09-05T18:14:08.232Z</atom:updated>
            <content:encoded><![CDATA[<p>In 2008, a person still unknown, going by the name <em>Satoshi Nakamoto</em> published the first blockchain, inventing the first decentralized digital currency, <em>Bitcoin</em> (Nakamoto, 2008). By definition:</p><blockquote>The blockchain is an incorruptible digital ledger of economic transactions that can be programmed to record not just financial transactions but virtually everything of value. (Tapscott, 2016)</blockquote><p>A <em>block</em> here refers to a set of transactions and as its name suggests, the <em>blockchain</em> creates a chain of blocks, each block links back to its previous block through its hash, forming a chain back to the first (<em>genesis</em>) block. In this way, <em>transactions</em> can be added securely if the nodes on the network are in <em>consensus</em> on what the hash should be. It’s safer than any of the centralized payment systems because, the only way to make changes would be to hack more than half of the nodes in the blockchain, which, is why it is more secure to have more nodes/computers running the blockchain. Also, it allows for peer-to-peer transactions that do not need a third party, such as PayPal or a bank.</p><p>The Usage of digital coins:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*VrTnNirYQA37IWeH" /></figure><p>Digital coins are generally used in the same way as a real-life coin is — as money. You can think of coins like Bitcoin, Litecoin, and Monero just like the coins in your wallet or piggy bank can be used to pay for goods and services all over the internet and in many real-world places too. Other than these monetary uses, there is no other use for Bitcoin.</p><p>However, some digital coins (such as Ether, NEO, and Stellar (XLM) have more features. Ether (ETH) is used to fuel transactions on the Ethereum network, similarly there are open-sourced solutions like Stellar powered by lumen (XLM) network. Industry price website CoinMarketCap (coinmarketcap, n.d.)lists over 900 different examples of coins. In the blockchain world, the <em>wallet</em> is like a bank account. It is usually referred by a unique address which is used to send money to and from it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AXB7EIrbMQGWeftp" /></figure><p>Blockchain is gaining its momentum with most of the circular economy based world-wide businesses, especially the ones who want to stay away from the hassle of handling cross-country finances, regulations and willing to let blockchain handle secure and timely transactions with the trust of all the parties involved. (Club, n.d.). One classic scenario is that Stellar (Stellar, n.d.) is used by most businesses, operating across countries, for their secure, fast, and timely multi-currency transactions with minimum charges. Empower (Empower, n.d.) for example, who is in plastic waste recycling uses the platform to pay their waste pickers worldwide in small incentives, quickly using their own defined tokens, without dealing with a 3rd party money exchangers saving money and time of all the stakeholders. The usual way of transferring money internationally involves increasing fees and usually takes more than a day for most of the developing countries with challenges on infrastructure. But the proper use of blockchain can save the trouble at both the sender and the receiver and make pathways to the modern cashless initiatives.</p><h3>References</h3><p>Club, C. C. (n.d.). Retrieved from <a href="https://www.cryptocurryclub.com/resources">https://www.cryptocurryclub.com/resources</a></p><p><em>coinmarketcap</em>. (n.d.). <a href="http://retrieved%20from%20https//coinmarketcap.com/currencies/dash/">Retrieved from https://coinmarketcap.com/currencies/dash/</a></p><p>Empower. (n.d.). Retrieved from <a href="https://ewts.empower.eco/">https://ewts.empower.eco/</a></p><p>Nakamoto, S. (2008). Bitcoin: A Peer-to-Peer Electronic Cash System. <a href="https://bitcoin.org/bitcoin.pdf"><em>https://bitcoin.org/bitcoin.pdf</em></a>.</p><p>Tapscott, D. &amp;. (2016). <em>Blockchain Revolution.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=680e72c2f8f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>