Once upon a course, there was a group of eager students who embarked on a journey of learning. They were filled with hope and excitement as they entered the classroom, ready to dive into new subjects and expand their knowledge. The course began with an introduction, setting the stage for what was to come. The students were introduced to the course syllabus, which outlined the topics that would be covered, along with the assignments and exams that awaited them. As the days turned into weeks, the students delved into the material with enthusiasm. They attended lectures, participated in group discussions, and pored over textbooks and articles.

Getting Started with Test Mode for Magic SDK

Magic client-side Web SDK provides Test Mode as a quick way to test your integration locally by asserting specific error codes or bypassing the magic link flow completely.

# Usage

To enable Test Mode, provide testMode: true to the SDK constructor.

01import  Magic > from 'magic-sdk'; 

03 const magic = new Magic('YOUR_API_KEY',  

04 testMode: true, 

With Test Mode enabled, you can assert the desired behavior through the email address you provide to loginWithMagicLink .

To assert a success state, use [email protected] .

Users created in test mode are ephemeral. It is advised that you do not associate these users to persistent data in your backend. If you are building an integration with cryptocurrency or Web3 features, please take a look at the advanced usage section below.

To assert a failed state, use [email protected] .

To assert a case-specific failed state, you can also provide an RPC error code with [email protected] .

01import  RPCErrorCode > from 'magic-sdk'; 

03magic.auth.loginWithMagicLink( email: `test+fail_with_$RPCErrorCode.MagicLinkFailedVerification>>@magic.link` >); 

04magic.auth.loginWithMagicLink( email: `test+fail_with_$RPCErrorCode.MagicLinkExpired>>@magic.link` >); 

05magic.auth.loginWithMagicLink( email: `test+fail_with_$RPCErrorCode.MagicLinkRateLimited>>@magic.link` >); 

You can find a list of relevant RPC error codes here .

# Advanced Usage

Web3 and blockchain use-cases sometimes require access to deterministic key-pairs so that testnet funds are available at runtime. To enable this, users can explicitly specify the key-pair associated to a test user, like so:

01[email protected]

The key-pair provided in the email address during test mode is not protected by Magic's delegated key management system. These keys should not be considered secure or private. Never store mainnet funds with these keys!

In practice, you can assert a successful login with:

01magic.auth.loginWithMagicLink( 

02 email: 

03 '[email protected]', 

In the example above, we encode an Ethereum-compatible key-pair in the test user's email address. The login method will immediately resolve with a success state, bypassing the passwordless flow and enabling Ethereum or EVM-compatible signing methods to work seamlessly with your existing Web3 code.

# Expected Behavior

Client-side Web SDK methods

• The loginWithMagicLink method from the Auth Module will be the only login option to assert the desired behavior. Passing [email protected] into the loginWithEmailOTP method will throw an RPCError .
• Attempting to change the email address via use of the updateEmail method from the User Module will throw an RPCError .
• You can generate a new DID token via use of the getIdToken or generateIdToken methods from the User Module.
• Calling the getMetadata method from the User Module while [email protected] is logged in will return the following;

02 issuer: 'did:ethr:0x1e9FF803fFA22209A10A087cc8361d4aa3528c45', 

03 publicAddress: '0x1e9FF803fFA22209A10A087cc8361d4aa3528c45', 

• Calling the isLoggedIn method from the User Module will return a boolean value after checking if [email protected] is currently logged in.
• Calling the logout method from the User Module will log [email protected] out.

Server-side SDK methods

• magicClient.auth.loginWithMagicLink(< email: '[email protected]' >) resolves to a DID token that is not valid to all server-side SDK methods.
• Passing the DID token to the validate method from the Token Module will throw an IncorrectSignerAddress error.
• Passing the DID token to the getIssuer method from the Token Module will return the following;

02 issuer: "did:ethr:0x1e9FF803fFA22209A10A087cc8361d4aa3528c45" 

• Passing the DID token to the getPublicAddress method from the Token Module will return the following;

Magic JavaScript SDK

The Magic JavaScript SDK empowers developers to provide frictionless web3 onboarding to their end-users while preserving their security and privacy using non-custodial wallets.

They attended lectures, participated in group discussions, and pored over textbooks and articles. They formed study groups, seeking support and collaboration from their classmates. The course offered a variety of learning activities to keep the students engaged.

📖 Documentation

• See the developer documentation to learn how you can master the Magic SDK in a matter of minutes.
• See the @magic-sdk/react-native-bare README for Bare React Native package specific information.
• See the @magic-sdk/react-native-expo README for Expo React Native package specific information.

They worked on projects, conducted experiments, and solved real-world problems. The instructor challenged them with thought-provoking questions and encouraged them to think critically and creatively. Along the way, the students faced challenges and obstacles. Some concepts were difficult to grasp, while others required hours of practice and repetition. But they persevered, seeking help when needed and pushing through the difficulties. As the course reached its midpoint, the students began to see the progress they had made. They had developed a deeper understanding of the subject matter and could apply their knowledge in practical ways. They started to feel a sense of accomplishment and pride in their work. The course also provided opportunities for personal growth. The students developed communication and teamwork skills as they collaborated on group projects. They honed their time management and organization skills to meet deadlines and balance multiple assignments. As the final weeks of the course approached, the students focused on review and preparation for the upcoming exams. They gathered their notes and created study guides, spending long hours in the library and their study spaces. They supported each other, quizzing and explaining concepts to ensure everyone was well-prepared. Finally, the day of the final exam arrived. The students entered the classroom with a mix of nervousness and confidence. They knew they had put in the effort and were ready to showcase their knowledge. As they wrote their answers, they felt a sense of accomplishment knowing how far they had come. With the course now over, the students reflected on their journey. They realized that this course had been more than just about gaining knowledge. It had taught them resilience, perseverance, and the value of hard work. They had formed new friendships, discovered their passions, and grown both academically and personally. Once upon a course, a group of students embarked on a journey that transformed their lives. They emerged as more knowledgeable, skilled, and confident individuals, ready to take on new challenges and continue their quest for lifelong learning..

Reviews for "The Curse of the Magic Book: Unlocking its Secrets"

1. Amanda - 2 stars - Once Upon a Curse was a disappointment for me. The storyline felt weak and predictable, and the characters were flat and lacked depth. I found it hard to connect with any of them. The writing style was also bland and lacked the creativity and imagination I was expecting from a fantasy novel. Overall, I was left feeling underwhelmed and wouldn't recommend it to fellow readers looking for a gripping and captivating read.

2. Max - 2 stars - Once Upon a Curse failed to live up to the hype for me. The pacing was slow, and the plot seemed to meander without a clear direction. The world-building was also lacking, with little description or development of the fantasy realm. The characters, while initially intriguing, quickly became one-dimensional and fell into clichéd tropes. I struggled to stay engaged with the story and ultimately felt unsatisfied with the resolution. Overall, I found Once Upon a Curse to be forgettable and wouldn't recommend it to avid fantasy readers.

3. Sophie - 3 stars - Once Upon a Curse had some potential, but it fell short for me. The concept was interesting, blending fairy tale elements with a cursed world, but the execution lacked finesse. The writing was average at best, with clunky dialogue and repetitive descriptions. The romance subplot felt forced and underdeveloped, taking away from the main plot. While there were a few exciting moments, overall, the story failed to hold my attention. I wanted to like Once Upon a Curse more than I did, but unfortunately, it didn't meet my expectations.

The Mysterious Curse: Solving the Puzzle