SPDX license and pragma version in Blockchain / Solidity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the SPDX license identifier.

Blockchain / Solidity

// SPDX-License-Identifier: [1]
pragma solidity ^0.8.0;

Drag options to blanks, or click blank then click option'

AMIT

BGPL-3.0

CApache-2.0

DBSD-3-Clause

Attempts:

3 left

💡 Hint

Common Mistakes

Using a license identifier that is not recognized by SPDX.

Forgetting to include the SPDX license line at the top of the file.

The SPDX license identifier MIT is commonly used to specify the license of the Solidity file.

2fill in blank

medium

Complete the code to specify the Solidity compiler version pragma.

Blockchain / Solidity

pragma solidity [1]0.8.17;

Drag options to blanks, or click blank then click option'

A>=

B~

C^

D<=

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong symbol that allows incompatible compiler versions.

Omitting the pragma version line.

The caret symbol ^ means the compiler version can be 0.8.17 or higher but less than 0.9.0.

3fill in blank

hard

Fix the error in the SPDX license identifier line.

Blockchain / Solidity

// SPDX-License-Identifier: [1]
pragma solidity ^0.8.0;

Drag options to blanks, or click blank then click option'

AMIT License

BMIT

Cmit

DMIT-License

Attempts:

3 left

💡 Hint

Common Mistakes

Writing the license name in lowercase.

Adding extra words like 'License' or hyphens.

The SPDX license identifier must be in uppercase and exactly MIT without extra words or hyphens.

4fill in blank

hard

Fill both blanks to specify a license and a compatible pragma version.

Blockchain / Solidity

// SPDX-License-Identifier: [1]
pragma solidity [2]0.8.12;

Drag options to blanks, or click blank then click option'

AApache-2.0

B~

C^

DGPL-3.0

Attempts:

3 left

💡 Hint

Common Mistakes

Using an invalid license identifier.

Using a wrong symbol for the pragma version.

The license Apache-2.0 is valid and the caret ^ allows compatible compiler versions starting from 0.8.12.

5fill in blank

hard

Fill all three blanks to specify the SPDX license, pragma version, and a fixed compiler version.

Blockchain / Solidity

// SPDX-License-Identifier: [1]
pragma solidity [2]0.8.10;
pragma solidity [3]0.8.10;

Drag options to blanks, or click blank then click option'

AGPL-3.0

B>=

C==

DMIT

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid SPDX license strings.

Using incorrect symbols for pragma version constraints.

The SPDX license is MIT. The first pragma uses >= to allow compiler versions 0.8.10 or higher, and the second pragma uses == to fix the compiler version exactly at 0.8.10.

Practice

1.

What is the purpose of the SPDX-License-Identifier line in a Solidity smart contract?

easy

A. To specify the license type of the contract's source code

B. To set the Solidity compiler version

C. To declare the contract's owner

D. To define the contract's storage variables

Solution

1. Step 1: Understand SPDX-License-Identifier usage

   The SPDX-License-Identifier line is a comment that clearly states the license under which the source code is released.

2. Step 2: Differentiate from pragma version

   Unlike pragma which sets compiler version, SPDX is about legal licensing information.

3. Final Answer:

   To specify the license type of the contract's source code -> Option A

4. Quick Check:

   SPDX-License-Identifier = License type [OK]

Hint: SPDX line always shows license info, not compiler version [OK]

Common Mistakes:

• Confusing SPDX line with pragma version
• Thinking SPDX sets compiler behavior
• Ignoring SPDX line as just a comment

2.

Which of the following is the correct way to specify the Solidity compiler version to accept any version from 0.8.0 up to but not including 0.9.0?

pragma solidity ?;

easy

A. pragma solidity ^0.8.19;

B. pragma solidity 0.8.0;

C. pragma solidity >=0.8.0 <0.9.0;

D. pragma solidity >0.8.0 <=0.9.0;

Solution

1. Step 1: Understand version range syntax

   The syntax >=0.8.0 <0.9.0 means any version from 0.8.0 up to but not including 0.9.0.

2. Step 2: Compare with caret (^) operator

   The ^0.8.19 syntax allows >=0.8.19 <0.9.0, excluding earlier 0.8.x versions like 0.8.0. The explicit range >=0.8.0 <0.9.0 matches exactly.

3. Final Answer:

   pragma solidity >=0.8.0 <0.9.0; -> Option C

4. Quick Check:

   Version range syntax = >=0.8.0 <0.9.0 [OK]

Hint: Use >= and < to specify exact version range [OK]

Common Mistakes:

• Using exact version without range
• Misplacing comparison operators
• Confusing caret (^) with range syntax

3.

What will happen if you compile this Solidity code snippet?

// SPDX-License-Identifier: MIT
pragma solidity ^0.7.0;
contract Test {
  uint public x = 5;
}

Assuming you use Solidity compiler version 0.8.10.

medium

A. Compilation fails due to pragma version mismatch

B. Compilation fails due to SPDX license missing

C. Compilation succeeds but with a warning

D. Compilation succeeds without errors

Solution

1. Step 1: Check pragma version compatibility

   The pragma ^0.7.0 means compiler versions from 0.7.0 up to but not including 0.8.0 are allowed.

2. Step 2: Compare with compiler version used

   Compiler version 0.8.10 is outside the allowed range, so compilation will fail due to version mismatch.

3. Final Answer:

   Compilation fails due to pragma version mismatch -> Option A

4. Quick Check:

   Pragma ^0.7.0 excludes 0.8.10 = mismatch [OK]

Hint: Compiler version must fit pragma range exactly [OK]

Common Mistakes:

• Ignoring pragma version mismatch
• Thinking SPDX license affects compilation
• Assuming caret (^) allows all newer versions

4.

Identify the error in this Solidity contract header:

// SPDX-License-Identifier MIT
pragma solidity ^0.8.0;
contract Sample {}

medium

A. SPDX license identifier must be in quotes

B. Incorrect pragma version syntax

C. Contract name must be lowercase

D. Missing colon ':' after SPDX-License-Identifier

Solution

1. Step 1: Check SPDX license line format

   The SPDX license line must be in the format // SPDX-License-Identifier: LicenseName with a colon after the identifier.

2. Step 2: Verify other parts

   The pragma syntax and contract name are correct; SPDX license identifier does not require quotes.

3. Final Answer:

   Missing colon ':' after SPDX-License-Identifier -> Option D

4. Quick Check:

   SPDX line requires colon ':' [OK]

Hint: SPDX line always has colon after identifier [OK]

Common Mistakes:

• Omitting colon after SPDX-License-Identifier
• Adding quotes around license name
• Thinking contract names must be lowercase

5.

You want to write a Solidity contract that is compatible with any compiler version from 0.6.0 up to but not including 0.9.0, and you want to specify the MIT license. Which of the following headers is correct?

hard

A. // SPDX-License-Identifier: MIT
pragma solidity 0.6.0;

B. // SPDX-License-Identifier: MIT
pragma solidity >=0.6.0 <0.9.0;

C. // SPDX-License-Identifier MIT
pragma solidity ^0.6.0;

D. // SPDX-License-Identifier: MIT
pragma solidity >=0.6.0 <=0.9.0;

Solution

1. Step 1: Check SPDX license line correctness

   The SPDX line must have a colon after the identifier and specify the license, so // SPDX-License-Identifier: MIT is correct.

2. Step 2: Verify pragma version range

   The pragma >=0.6.0 <0.9.0 correctly specifies compatibility from 0.6.0 up to but not including 0.9.0. Using <=0.9.0 would include 0.9.0, which is not desired.

3. Final Answer:

   // SPDX-License-Identifier: MIT pragma solidity >=0.6.0 <0.9.0; -> Option B

4. Quick Check:

   SPDX with colon + correct pragma range = // SPDX-License-Identifier: MIT pragma solidity >=0.6.0 <0.9.0; [OK]

Hint: Use colon in SPDX and < for upper pragma bound [OK]

Common Mistakes:

• Omitting colon in SPDX line
• Using exact version instead of range
• Including upper bound version with <= instead of <