Xverse is the leading Bitcoin wallet for Web3, providing first-class support for Ordinals, NFTs, DeFi and decentralized applications. With a beautifully designed, easy-to-use wallet available on iOS, Android and desktop as a Chrome browser extension, Xverse lets users securely manage Bitcoin on layer 1 as well as layer 2 networks like Stacks, and soon, the Lightning Network. Xverse is a global community of amazingly talented colleagues dedicated to making the world a better place with blockchain technology. Our mission is to empower people to control their data and wealth by delivering a more accessible, user-owned internet and decentralized economy for all.

Secret Key Labs

Hey Hackers, Cypherock has been nominated in HackerNoon's annual awards in New Dehli, India. Startup of the Year Please vote for us here: https://hackernoon.com/startups/asia/asia-new-delhi-dl-india Read more about us below to understand why we deserve your vote. Meet Cypherock The current issues with key management pose massive barriers to the adoption of decentralized technologies. We believe digital assets will have exponentially more value in the future and that will just not be limited to Cryptocurrency. Our mission is to empower people to be self-sovereign and to have the same peace of mind and control with their crypto and personal data that they have with their savings in the bank vaults. Cypherock X1 decentralizes the private keys into 5 cryptographic parts, each stored on tamper resistant hardware units - 1 Cypherock X1 vault and 4 X1 cards. You need only the vault and any 1 of the X1 Cards to make a transaction. Even if you lose any 3 out of these 5 units, your funds are still safe. Also you can set a pin during the setup process which is an additional layer of security. Cypherock X1 is scrutinized by WalletScrutiny and audited by KeyLabs, the security firm that has found vulnerabilities in Trezor, Ledger, etc. Rohan Agarwal and Vipul Saini - Co-founders of Cypherock Rohan has been developing software since 2014 and has been in the Crypto space since 2017. He has worked with organizations such as Blockgeeks, Fossasia (Google Summer of Code), Apollo Munich, Siftr Labs (acq.), and Samsung amongst others. He is a generalist by nature having worked across both technical and non-technical roles in the past. Vipul has been in the Crypto space since 2017 and specializes in Hardware Security & Embedded engineering since 2012. He has worked in partnership with Lockheed Martin on an Autonomous drone project and was the 1st employee in Nymble Labs, a VC-backed food robotics startup based out of SF, USA. He likes to dabble in frontier technologies and prefers spending time solving deep technical problems that have the most impact. How We're Disrupting/Improving the Web3 Industry We are building the world’s safest hardware wallet for crypto and NFT storage - Cypherock X1, funded and backed by Consensys Labs, Sandeep Nailwal (co-founder of POLYGON), and others. Cypherock X1 stands out among hardware wallets as an innovative and secure solution for storing cryptocurrencies. X1 is audited by Keylabs and scrutinized by Wallet Scrutiny. It introduces a seedless security model, utilizing Shamir’s Secret Sharing scheme to divide the private key into multiple shares. This approach enhances security by eliminating the risks associated with seed phrases, which can be lost, stolen, or compromised. Cypherock X1 offers a seamless user experience. The device and the software ‘CySync’ that comes along with Cypherock X1 boast a user-friendly interface, making it easy for both beginners and experienced users to navigate and manage their crypto assets in a single app. Its compact and portable design allows users to carry their wealth securely wherever they go, without compromising on convenience. Standing Out from The Crowd Firstly, serves not only as a hardware wallet but also as a secure seed phrase backup solution for multiple wallets. It allows users to store the recovery seeds of various wallets, thereby providing a consolidated and reliable backup for all their cryptocurrency holdings. This feature ensures that even if you have multiple wallets, you can securely manage their seed phrases in one centralized device, reducing the risk of losing access to any of your wallets. Secondly, Portfolio Management of Multiple Wallets: Cypherock X1 goes beyond being just a cold wallet by offering robust portfolio management capabilities. With the device, users can import multiple wallets and conveniently manage their entire cryptocurrency portfolio from a single interface. This unified view allows for easy monitoring of overall portfolio performance across different wallets and blockchain networks. By consolidating portfolio management, Cypherock X1 streamlines the user experience and provides a holistic approach to cryptocurrency asset management. Cypherock X1 also provides comprehensive multichain support, allowing users to securely store and manage a wide range of cryptocurrencies and blockchain assets in a single device. Whether you hold Bitcoin, Ethereum, or other popular cryptocurrencies, Cypherock X1 has you covered. The next feature that sets us apart is the beneficiary service. You have to safeguard your Crypto while you are alive and only transfer them after you are dead which is impossible if you are the only one knowing your keys. Cypherock eliminates fear around loss of Crypto in case you die. With our beneficiary service, the assets can be transferred without Cypherock or any other party ever knowing the amount you HODL in the X1 wallet (Go Privacy!). Cypherock X1 Our Predictions/Thoughts on the Web3 Industry in 2023 : Recognizing the importance of seamless key management, innovative solutions will emerge to simplify the user experience. User-centric key management tools will provide enhanced security while being more accessible and intuitive. These solutions will offer convenient ways to securely store, manage, and interact with various types of digital assets beyond cryptocurrencies, including non-fungible tokens (NFTs), decentralized finance (DeFi) assets, and more. User-Centric Key Management Solutions : Interoperability will play a crucial role in the maturation of the Web3 ecosystem. We can expect increased efforts towards establishing common standards and protocols that enable seamless interaction and interoperability among different decentralized applications (dApps) and platforms. This will facilitate the exchange and utilization of digital assets across various Web3 networks, fostering a more interconnected and efficient decentralized ecosystem. Interoperability and Standardization : In 2023, we can anticipate a significant surge in the adoption of decentralized applications by mainstream users. As user interfaces and experiences improve, more individuals will begin to explore and embrace decentralized alternatives to traditional centralized platforms. Decentralized social media platforms, decentralized finance applications, and decentralized marketplaces will witness increased usage, driven by user demand for privacy, security, and ownership of their data. Mainstream Adoption of Decentralized Applications : The potential of Web3 extends far beyond the financial sector. In 2023, we will witness the emergence of innovative and disruptive use cases across various industries such as healthcare, supply chain management, gaming, and digital identity. Decentralized technologies will revolutionize these sectors by enhancing transparency, security, and efficiency, ultimately transforming how we interact and transact in the digital realm. Expanding Use Cases : With the growing prominence of Web3 and the increasing value associated with digital assets, regulatory frameworks will continue to evolve. Governments and regulatory bodies will seek to strike a balance between fostering innovation and ensuring consumer protection. We can expect to see clearer guidelines and regulations addressing areas such as digital asset ownership, taxation, identity management, and consumer rights within the Web3 landscape. Regulatory Evolution What word defines the state of Web3 in 2023? : Web3's impact will be transformative across various aspects of society, economy, and technology. In 2023, we will witness the tangible effects of decentralization, as it reshapes industries and redefines traditional systems. The decentralized finance (DeFi) space will continue to expand, offering a wide array of financial services that are accessible, transparent, and resistant to censorship. The concept of digital ownership will become more prominent, with non-fungible tokens (NFTs) revolutionizing the art, gaming, and collectibles markets. Moreover, Web3 will drive innovation in areas such as supply chain management, healthcare, digital identity, and governance, transforming the way these industries operate. As more individuals and organizations embrace the principles of Web3, the collective shift towards a decentralized, open, and user-centric internet will have far-reaching implications for how we interact, transact, and collaborate in the digital realm. Transformative Why we decided to participate in HackerNoon's Startup of the Year awards We have decided to participate for three main reasons. : HackerNoon is a reputable platform known for its coverage of technology, startups, and innovation. Participating in their Startup of the Year awards offers Cypherock an opportunity to gain industry recognition and exposure. Being associated with a respected platform like HackerNoon can help elevate Cypherock's visibility and credibility within the startup ecosystem, attracting potential investors, partners, and customers. Industry Recognition : Participating in the awards allows Cypherock to expand its network and connect with other startups, industry experts, and influencers. Engaging with the startup community through such events opens doors for valuable collaborations, knowledge sharing, and partnerships. The networking opportunities provided by HackerNoon's Startup of the Year awards can lead to meaningful relationships that contribute to Cypherock's growth and development. Network Expansion : The Startup of the Year awards provide a platform for Cypherock to showcase its innovative solutions and receive feedback from industry experts and judges. The evaluation process can validate Cypherock's accomplishments, product offerings, and market potential. Constructive feedback and insights from experienced professionals can help refine Cypherock's strategies, identify areas for improvement, and strengthen its value proposition. Validation and Feedback Final Thoughts is a next-generation hardware wallet and key management solution that prioritizes the secure storage and management of digital assets in the decentralized era. With its advanced features and robust security measures, Cypherock offers users a reliable and user-friendly solution for safeguarding cryptocurrencies, non-fungible tokens (NFTs). Cypherock Beyond its role as a cold wallet, Cypherock empowers users with portfolio management capabilities, enabling them to import and manage multiple wallets from a single interface. This consolidated approach simplifies the management of digital assets and enhances the user experience. Even if users have multiple other wallets, they can store up to 4 seed phrases using Cypherock X1. X1 is compatible with Metamask, Ledger, Trezor, etc, and can act as a seed phrase backup as well as a multi-wallet portfolio manager! Cypherock has been nominated as Startup of the Year in New Delhi, India. Vote for us today!

Empowering Self-Sovereignty - Interview with Startups of the Year Nominee, Cypherock 

Empowering Self-Sovereignty - Entrevista con el nominado a Startups del año, Cypherock

Renforcer l'auto-souveraineté - Entretien avec le nominé des startups de l'année, Cypherock

स्व-संप्रभुता को सशक्त बनाना - वर्ष के नामांकित व्यक्ति, साइफरॉक के स्टार्टअप के साथ साक्षात्कार

自己主権の強化 - スタートアップ オブ ザ イヤーにノミネートされた Cypherock へのインタビュー

Fortalecendo a autossoberania - Entrevista com o candidato a startups do ano, Cypherock

Trao quyền cho chủ quyền tự chủ - Phỏng vấn Ứng cử viên khởi nghiệp của năm, Cypherock

赋予自我主权 - 采访年度初创公司提名者 Cypherock

Late last year, after facing for its practices, Facebook announced : Companies buying ads would no longer be able to target people based on interest categories like race, religion, health conditions, politics, or sexual orientation. years of criticism a change to its multibillion-dollar advertising system See our data here. GitHub More than three months after the change purportedly went into effect, however, The Markup has found that such ad targeting is very much still available on Facebook’s platform. Some obvious ad categories have indeed been removed, like “young conservatives,” “Rachel Maddow,” “Hispanic culture,” and “Hinduism”—all categories we found as options on the platform back in early January but that have since disappeared. However, other obvious proxies for race, religion, health conditions, and sexual orientation remain. As far back as 2018, CEO Mark Zuckerberg the company had “removed the ability to exclude ethnic groups and other sensitive categories from ad targeting. So that just isn’t a feature that’s even available anymore.” told Congress The Markup found, however, that while “Hispanic culture” was removed, for example, “Spanish language” was not. “Tea Party Patriots” was removed, but “Tea party” and “The Tea Party” were still available. “Social equality” and “Social justice” are gone, but advertisers could still target “Social movement” and “Social change.” Starbucks, for example, was still able to use existing options after the change to place an ad for its pistachio latte focused on users interested in “Contemporary R&B,” “telenovela,” “Spanish language,” and “K-pop,” all proxies for Black, Latino, and Asian audiences on Facebook. Facebook hasn’t explained how it determines what advertising options are “sensitive” and, in response to questions from The Markup, declined to detail how it makes those determinations. But in the days after The Markup reached out to Facebook for comment, several more potentially sensitive ad-targeting options we flagged were removed by the company. “The removal of sensitive targeting options is an ongoing process, and we constantly review available options to ensure they match people’s evolving expectation of how advertisers may reach them on our platform,” Dale Hogan, a spokesperson for Facebook parent company Meta, said in a statement. “If we uncover additional options that we deem as sensitive, we will remove them.” Facebook’s ad targeting system is the not-so-secret key to the company’s massive financial success. By tracking users’ interests online, the company promises, advertisers can find the people most likely to pay for their products and services and show ads directly to them. But the company has faced blowback for offering advertisers “interest” categories that speak to more fundamental—and sometimes highly personal—details about a user. Those interests can be used in surprising ways to discriminate, from to to tracking users . excluding people of color from housing ads fueling political polarization with specific illnesses It’s obvious to everyone who is in the field that [removing a handful of terms deemed sensitive] is not a complete solution. Aleksandra Korolova, University of Southern California Facebook’s critics say the company has had ample opportunity to fix the problems with its advertising system, and trying to repair the platform by removing individual “sensitive” terms masks an underlying problem: The company’s platform might simply be too large and unwieldy to fix without more fundamental changes. Removing a handful of terms it deems sensitive just isn’t enough, according to Aleksandra Korolova, an assistant professor of computer science at the University of Southern California. “It’s obvious to everyone who is in the field that it’s not a complete solution,” she said. Clear Proxies for Removed Terms Are Still on Facebook The Markup gathered of potentially sensitive terms starting in late October, before Facebook removed any interest-targeting options. The data was gathered through , a project in which The Markup receives Facebook data from a national panel of Facebook users. a list Citizen Browser We also gathered a list of terms that Facebook’s tools recommended to advertisers when they entered a potentially sensitive term—the company suggested “BET” and “Essence (magazine)” when advertisers searched for “African American culture,” for example. Then, also using Facebook’s tools, we calculated how similar terms were to their suggestions by viewing how many users the ads were estimated to reach, which Facebook calls an “audience.” (See the details of our analysis .) on Github To find the gaps in Facebook’s cleanup process, we then searched those terms again in Facebook’s at the end of January to see which ones the company had removed following its change. public advertising tools In some cases, we found, options still available reached almost exactly the same users as options that were removed. “BET,” the acronym for Black Entertainment Television, was removed, but “BET Hip Hop Awards,” which was previously recommended with BET and had a 99 percent overlap in audiences, was still available. “Gay pride” was also removed as an option, but by using the term “RuPaul’s Drag Race,” advertisers could still reach more than 13 million of the same users. These proxies weren’t just theoretically available to advertisers on Facebook. The Markup found companies actively using them to target ads to people on the social network. Using , we found several examples of proxies for race and political affiliation used for targeting. Citizen Browser Ancestry, the genealogy service, for example, targeted ads using the terms “telenovela,” “BET Hip Hop Awards,” “African culture,” and “Afrobeat.” Facebook removed “Fox News Channel” as a targeting option that could reach conservative users, but we saw the conservative satire website The Babylon Bee targeting an ad ridiculing Anthony Fauci using the then-still-available interest category “Judge Jeanine Piro,” a Fox News personality. Before Fox News Channel was removed, we found 86 percent of users tagged with an interest in Judge Jeanine Piro were also tagged with an interest in the cable news network. Facebook also failed to fully eliminate targeting based on medical conditions, we found. “Autism Awareness” was removed, but “Epidemiology of autism” was still available. “Diabetes mellitus awareness” was removed, but the closely related “Sugar substitute” wasn’t. We found an ad from Medtronic, a medical device company, using that term to promote a diabetes management insulin pen on Facebook. Even Facebook itself has used the proxies. We found an ad placed by the company promoting its groups to users interested in “Vibe (magazine),” a stand-in for removed terms that target Black audiences. Starbucks, Ancestry, and the Babylon Bee didn’t respond to requests for comment on their ad-targeting practices. Pamela Reese, a spokesperson for Medtronic, said the company has stopped using “Sugar substitute” as a targeting option and that Medtronic is “well within” FDA regulations for advertising medical devices. The Markup provided several examples of these potential proxy terms to Facebook, including  “telenovela,” “BET Hip Hop Awards,” “RuPaul’s Drag Race,” and “Judge Jeanine Piro.” They were quietly removed after our request for comment was sent. Critics of Facebook like Korolova say Facebook has of promising to implement meaningful changes on its advertising platform only to fall short of the pledge. a track record Research has shown problems with advertising “proxies” for years, and Facebook could have taken stronger action to fix the problems, she argues. “If they wanted to, they could do better,” Korolova said. Facebook says its recent changes were needed to prevent abuse, but some organizations that say they use Facebook for social good have complained that the new policies put up barriers to their work. and have complained that the changes have limited their ability to reach a relevant audience. Climate activists medical researchers Daniel Carr, a recruitment consultant for SMASH Labs, a medical research group that uses Facebook to recruit gay and bisexual men for studies, said the recent changes forced them to switch from terms like “LGBT culture” to pop culture references like “RuPaul’s Drag Race.” Carr said study recruitment was steady, but the change didn’t sit right with them. “It’s made it more complicated on our side, and it’s not actually changed anything, other than Facebook can now say, ‘We don’t allow you to target by these things,’ ” Carr said. “It’s a political move, if anything.” By and Angie Waller Colin Lecher Also published here Photo by on Dima Solomin Unsplash

Facebook Made a Promise. Did They Keep It?

Facebook hizo una promesa. ¿Lo mantuvieron?

Facebook a fait une promesse. L'ont-ils gardé ?

फेसबुक ने किया वादा क्या उन्होंने इसे रखा?

Facebookは約束をしました。彼らはそれを維持しましたか？

O Facebook fez uma promessa. Eles o guardaram?

Facebook đã thực hiện một lời hứa. Họ có giữ nó không?

Facebook 做出了承诺。他们保留了吗？

If you're reading this, you probably know what a CI/CD pipeline is. If you don't, no big deal -- it's just yet another acronym. CI/CD short for "continuous integration and continuous delivery", which when we boil it down, simply means that everything between your git commit and a deployment works auto-magically so you can rest your fingers and watch some Netflix. In this example, I'm going to be focusing on deploying a static HTML website, but you really could do this for any sort of web application front-end. We will be highlighting how to do this using AWS, Terraform and Gitlab. Let me just explain real quick why we'd want to do this. First, this makes your life easier. You write the code, you make a commit, push, and your pipeline deletes old files from your S3 bucket, uploads the new files, sets permissions, and then invalidates your CloudFront distribution so that all you have to do is go look at your changes in production. Second, it removes human error. You can't forget to upload files or invalidate a CF if your code does it for you. Third, it speeds up your deployments because you no longer have to go ahead and do things manually. For all of these reasons, I always set up a pipeline for all of my personal and professional projects. Enough of me rambling; let's get to work. Prerequisites A account GitLab An account AWS is installed Terraform A account Keybase Set up the infrastructure I like to make things as easy and reproducible as possible, so we'll be using Terraform to build out the infrastructure. If you don't have Terraform installed, then you didn't read the prerequisites (tsk tsk...) and I'm going to need you to install it. For the website's infrastructure, all we'll need is an S3 bucket and a CloudFront distribution. We'll just use a default CloudFront certificate since we aren't connecting this distribution to our domain name in this example. Before we go any further, I would recommend creating a repository for all of your Terraform configs. It will just keep things more organized if you decide that you want to continue to use Terraform for configuring your infrastructure. Anyways... Create a file named main.tf and paste this into. You can change the bucket_name variable to whatever you want, just make sure you set this correctly later on in another file (you'll see as I've highlighted where it needs to be adjusted in the code snippet). {
  default // provider region }

resource bucket acl policy { : , : [
      { : , : , : , : , : }
  ]
}
EOF

  website index_document error_document }
}

locals s3_origin_id }

resource origin domain_name origin_id }

  wait_for_deployment enabled is_ipv6_enabled default_root_object default_cache_behavior allowed_methods cached_methods target_origin_id forwarded_values query_string cookies forward }
    }

    viewer_protocol_policy min_ttl default_ttl max_ttl }


  price_class restrictions geo_restriction restriction_type }
  }

  custom_error_response error_code error_caching_min_ttl response_code response_page_path }

  viewer_certificate cloudfront_default_certificate }
} variable "bucket_name" = "website.example.com" change this} "aws" { = "us-east-1" "aws_s3_bucket" "bucket" { = "${var.bucket_name}" = "private" = <<EOF "Version" "2012-10-17" "Statement" "Sid" "AddPerm" "Effect" "Allow" "Principal" "*" "Action" "s3:GetObject" "Resource" "arn:aws:s3:::${var.bucket_name}/*" { = "index.html" = "index.html" { = "S3-${var.bucket_name}" "aws_cloudfront_distribution" "s3_distribution" { { = "${aws_s3_bucket.bucket.bucket_regional_domain_name}" = "${local.s3_origin_id}" = false = true = true = "index.html" { = [ "DELETE" , "GET" , "HEAD" , "OPTIONS" , "PATCH" , "POST" , "PUT" ] = [ "GET" , "HEAD" ] = "${local.s3_origin_id}" { = false { = "none" = "redirect-to-https" = 0 = 3600 = 86400 = "PriceClass_100" { { = "none" { = 403 = 0 = 200 = "/index.html" { = true Now run the config create the infrastructure: terraform init
terraform - -approve apply auto Awesome! All of our infrastructure is set up in AWS and now we just need to set up our GitLab runner! Configure our Runner For this part, you'll need a GitLab repository for us to work with, so create a new one before proceeding. Now that you have a repository, let's set up our runner. We're going to use a shared runner from GitLab. They're free to use up for up to 2,000 minutes of deployments per month -- and they're enabled by default. I've found that they're somewhat slow and it stinks that you're throttled at 2,000 minutes, so I usually use my own runners spun up in Kubernetes or on EC2 instances, but let's save that for another tutorial. We need to supply the runner with an AWS IAM user to use to deploy to S3. Create another terraform config with this content: {
  description default // provider region }


resource user pgp_key }

resource name user policy { : , : [
        { : , : [ ], : },
        { : , : [ , , , , ], : [ },
        { : , : , : }
    ]
}
EOF
}

resource name }

output value }

output value } variable "keybase_user" = "A keybase username to encrypt the secret key output." = "dannextlinklabs" change this} "aws" { = "us-east-1" "aws_iam_access_key" "gitlab_ci" { = "${aws_iam_user.gitlab_ci.name}" = "keybase:${var.keybase_user}" "aws_iam_user_policy" "gitlab_ci" { = "gitlab-ci-policy" = "${aws_iam_user.gitlab_ci.name}" = <<EOF "Version" "2012-10-17" "Statement" "Effect" "Allow" "Action" "s3:ListBucket" "Resource" "*" "Effect" "Allow" "Action" "s3:PutObject" "s3:PutObjectAcl" "s3:GetObject" "s3:GetObjectAcl" "s3:DeleteObject" "Resource" "arn:aws:s3:::website.example.com/*" // this needs to be set to your bucket name            ] "Effect" "Allow" "Action" "cloudfront:*" "Resource" "*" "aws_iam_user" "gitlab_ci" { = "gitlab-ci" "access_key" { = "${aws_iam_access_key.gitlab_ci.id}" "secret_access_key" { = "${aws_iam_access_key.gitlab_ci.encrypted_secret}" Make sure you set the keybase user to your own keybase user, because Terraform uses that to encrypt the IAM user's secret access key. This won't work if you don't have a Keybase account, or if you try to use my Keybase account. Run the config. terraform init
terraform - -approve apply auto The terraform config returns an access key and an encrypted secret key for this user. We need to decrypt the secret key with the command (this is why you needed to use your own keybase user). terraform output encrypted_secret | --decode | pgp decrypt base64 keybase Now that we have the access key and the secret key for our GitLab user, we just to supply these variables to our runner by adding them to the variables section in the CI/CD settings. We need to set three variables in GitLab: AWS_ACCESS_KEY_ID - the access key that Terraform returned us
AWS_SECRET_ACCESS_KEY - the access key we just decrypted
AWS_DEFAULT_REGION - us-east-1 to to secret Create our super-duper simple website We have an empty repository set up with our GitLab runner enabled, so l Super cool website! Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore
      magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo
      consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
      Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. < > html < > body < > h1 </ > h1 < > p </ > p </ > body </ > html Commit that and push it to the repo, and that will be all we need for the "design". Run a Deployment GitLab CI/CD is based around a file called .gitlab-ci.yml. GitLab requires that file to be located in the root of your project. Our file needs to look like this: stages:
  - - variables:
  AWS_BUCKET: website.example.com // change this if necessary
deploy_s3:
  image: python:3.6
  stage: deploy-s3
  tags:
    - - before_script:
    - script:
    - only:
    - deploy_cf:
  image: python:3.6
  stage: deploy-cf
  tags:
    - - before_script:
    - script:
    - - only:
    - deploy-s3 deploy-cf docker gce pip install awscli -q aws s3 sync . / --delete --acl public-read s3: /$AWS_BUCKET/ master docker gce pip install awscli -q export distId=$(aws cloudfront list-distributions --output=text --query ] cut -f1) 'DistributionList.Items[*].[Id, DefaultCacheBehavior.TargetOriginId' | grep "S3-$AWS_BUCKET" | read -r dist; aws cloudfront create-invalidation --distribution-id $dist --paths ; done <<< while do "/*" "$distId" master This gitlab-ci file sets up two stages: deploy-s3, and deploy-cf. The first stage uploads our website to the S3 bucket, and the second invalidates the CloudFront distribution for that bucket in order to present the new changes to our website! This simple configuration is all you need to have a complete CI/CD pipeline for your business' website. Commit and push those changes, and then check out the pipelines section under the CI/CD tab in that project. You should see a deployment running. Success! You have a working CI/CD pipeline. Now, whenever you commit code to the master branch, GitLab will auto-magically upload and distribute your changes! Daniel Slapelis is a Devops Engineer with NextLink Labs, a Pittsburgh-based Devops and full stack engineering company.

Learn How to Build a CI/CD Pipeline Using GitLab for your Website

By: Blockchain Developer Jesse Abramowitz In order for a ecosystem to thrive, developers need to be on board to create and foster a community. Accomplishing that feat requires the appropriate tools to handle the job. From creating DApps using Ethereum, Hyperledger or even , a blockchain becomes mainstream only when the proper tools are in place for developers to allow for mass adoption. Blockchain Bitcoin Here at , some of my favourite work is building developer tools for blockchains. We are passionate about tools and are always looking for more to build. I personally joined the company almost 4 months ago. I am what is known as a blockchain native developer as in I am self taught with solidity as a base language. BlockX Labs As a lot of people may know the gold standard for this is Ethereum. The job they have done making it easy for developers is nothing short of a miracle and is the secret-not-so-secret key to their success. We’ve curated the following list that every blockchain developer should know, and blockchains need for their ecosystems to succeed. Take a look at our Top 10 below! 1. Language This can be any language, but the virtual machine needs to be able to read it and I need to be able to write it. It can go the route of blockchains like or and write their own or it can be like and use Javascript. Regardless, it has to be functioning. Ethereum Cardano BUMO An example is from Ethereum and is called . Solidity 2. Documentation and Education This is hands down the most important and sometimes most overlooked part of the equation. This is true for every tool but especially the language. How do I use it? What are the caveats? Is it an existing language? If so how is it different (for example can’t use non-deterministic code)? The more details the better. Documentation is key to allowing a Blockchain ecosystem to thrive because it allows developers everything they need to know about a blockchain. 3. Compiler Whatever virtual machine the specific blockchain uses it is not actually running the language that we are writing in. The code needs to be compiled down to bytecode then the virtual machine can act on it, so we need a tool to do that, which brings me to the next one. 4. Integrated Developer Environment for Ethereum is a very powerful tool. It is great for writing code and finding errors. It is also a great testing environment. Now technically you do not need to launch a whole browser based IDE like remix, instead you can create a plug in for existing IDE’s like VS code or Atom. However, I can attest to consistently using Remix for building and testing even though I have moved on to using for live deployments. Remix Truffle 5. Node as an API service To understand why this is needed, you have to understand some fundamental truths about the blockchain. One is that you can’t just connect and interact to this network. A blockchain (like the ones we are talking about) is a global state machine, so how can you read or interacting with it without knowing the state? You can’t. So how do you get the state?, That’s easy, you just run a node and sync it up on your laptop. Is that hard? Well lets just put it like this: To do this you need to start at the genesis block and run through every transaction locally that has ever happened on the blockchain. So, yes, very. Also do you want to turn off your laptop and go to bed? No problem, you just need to re-sync every new block the next day and dedicate a lot of laptop resources to it. This is ridiculous and very few developers would actually do this, so what we need is an endpoint. Someone who hosts their node over web sockets and allows you to access it to make calls and send transactions. For Ethereum the main endpoint service is called . Infura 6. Block Explorer How am I going to read the blockchain? It is a lot of code. For example, to figure out a list of transactions from an account you would have to iterate through the whole blockchain and then search for all instances of the . A block explorer can log and tag these files for searching to make it easy to access. A block explorer really is a visual representation of the blockchain. It is important both for users and developers. account 7. Browser Extensions Interface (Wallet) This extends to the idea of a new type of internet. One that uses peer-to-peer value transfer protocols as a standard at the very least. Preferably it will be used for more things. Currently DApps like use the blockchain for this exact purpose. One day, our browsers and phones will build in this functionality however; today we need to use a browser extension. Something that allows us to make constant calls to nodes and then send transactions to those nodes. gitcoin Example: AIWA for the Aion Network 8. Front-end to back-end library This one is mainly for developers. What we want are libraries. Things to make our front end easier and more flexible to write. By using Web3 js library I can easily make calls to the node I’m connected to. This makes developing the DApps that will bring value to your blockchain easier. 9. Testnet/Faucet There are many ways to test contracts and dapps. One way is to test it locally. This however lacks the dynamics of a live network and can only be considered as partial testing. You need a network that is free and acts in the exact same way as the mainnet you are going to. The closest we can get to this is testnets. Networks that are voluntary maintained and act in the same way as the mainnet. This also helps with testing forks as you can fork a test net before the mainnet. Example: Ropsten testnet. Although we have a testnet, I still need some of the native token to the blockchain to interact with it. I could always mine it but I want to move fast and reduce points of friction. You need a faucet a DApp that gives out tokens for free so developers can test. Example: **(**Built with ♥ by BlockX Labs) My Faucet 10. Token Standards (at least ERC20, ERC721 equivalents) ICOs dominated the crypto-sphere in 2017 and 2018. However, it i possible to use tokens for a multitude of reasons. Tokens themselves are complicated in terms of the rigorous security standards required. Not every developer can make a totally secure token nor should they have to use one in a larger application. The blockchain is new and hard to fully understand, it is also more permanent than other systems. Having standards that are well tested by a multitude of parties really help reduce security errors, to bring a blockchain into the mainstream and avoid hacks like the batch Overflow. Example: ERC-20 Bonus Couldn’t resist adding just one more! 11. Gas station Each transaction costs gas (for most cryptocurrencies). It is both an awesome feature and a drawback to these networks. It is important for users to be able to calculate how much gas they want to use based on the current state of the network. A nice visualization is beneficial. However, more important there needs to be an API that wallets can call to, to suggest an adequate gas price for users or else there will be a lot of dropped transactions. Example: Ethgasstation Conclusion I believe that these are the critical tools we believe will allow early-stage blockchain ecosystems to thrive. With these tools, developers will be able to experiment with different blockchains, develop DApps, and more. Are there any you think we missed? Let us know in the comments below! Jesse Abramowitz is a Blockchain Developer at BlockX Labs. He has worked on multiple DApps, projects, and Blockchain Networks. Currently, he is also a lab assistant at a local college and is always looking to help, teach and build on the blockchain. You can reach him at: jesse@blockxlabs.com

Top 10 Developer Tools for Blockchain Ecosystems

During my time at (a 30 week immersive full stack web development and CS program) I was exposed to everything from HTML/CSS, , ReactJS, ExpressJS, APIs, Python, Django, C, and much more. I learned and explored computer science topics like data structures, algorithms and time complexity. However, the particular topic I wanted to talk about and provide a tutorial on was a task I came across in my Lambda Labs project. Integrating Stripe Checkout with a client and an Express/Node server. Lambda School Javascript React When using Stripe Checkout there are two routes you can take, one time charge or subscription charge. I will cover the one time charge today. If you are interested in subscription charge, I will cover this in a future article. There is one step you need to do before we start coding. Create a account. This is a free account that is pretty quick to set up. I will wait here while you get that set up. Head back here once you are at your dashboard. Stripe Awesome so now you should be set up with a Stripe account. Take note the dashboard is in test mode. Keep it here until it’s time to take your project to production. Now let‘s start coding. Front End/Client Setup Let’s start with creating the client. I am going to use create-react-app to boilerplate our React app. Use the commands below in your terminal for setup. create-react-app stripe-clientcd stripe-clientyarn start You should now have a development server running in your terminal and be able to view your client in the new browser window. As you make and save changes to your app, the client in your browser will automatically refresh. Next we need to add all our libraries. In a new terminal, use the following commands to install the libraries. yarn add react-stripe-checkout axios Next lets create a component. This component will be a button that when clicked will open up the react-stripe-checkout modal. Follow the steps below. stripeBtn cd srctouch stripeBtn.js Create React Component Now copy and paste the following code for this component in the new folder and we will discuss details below. import React, { Fragment } from "react";import StripeCheckout from "react-stripe-checkout";import axios from "axios"; const stripeBtn = () => {const publishableKey = "pk_test_ZU3mlTy0q00DATc9EyF9A8jX"; const onToken = token => {const body = {amount: 999,token: token}; axios.post("http://localhost:8000/payment", body).then(response => {console.log(response);alert("Payment Success");}).catch(error => {console.log("Payment Error: ", error);alert("Payment Error");});}; return (<StripeCheckout ="Go Premium" ="Business LLC" ="Upgrade to a premium account today." ="Go Premium" ={999} ={onToken} ={publishableKey}image="https://www.vidhub.co" //Pop-in header imagebillingAddress={false}/>);}; label //Component button textname //Modal Headerdescription panelLabel //Submit button in modalamount //Amount in cents $9.99token stripeKey export default stripeBtn; To review what we have done above. We create a variable to hold our publishable key. You get this from your dashboard. From side bar click Developers>API Keys. This key is not a secret and does not need to be placed in an .env file. We have a function that we will cover in a moment. The component returns a element that comes from . The props passed are used to customize the modal and other transaction details. Make sure you include the prop onToken() StripeCheckout react-stripe-checkout stripeKey. The function “behind the scenes” sends the card info to Stripe and returns a token object. This object contains limited details about the transaction(card type, last 4 digits, email, etc.) Our function sends this token and the amount to our backend in the body with an axios request to finish the transaction. That is pretty much it. With React being modular, we can import the component in multiple places anywhere on our app. I am including the code below for the where I will import and render our component. onToken() App.js stripeBtn Final Steps and Finalize import React, { Component } from "react";import logo from "./logo.svg";import "./App.css";import StripeBtn from "./StripeBtn"; class App Component { extends render() {return (<div ="App"><header ="App-header"><img ={logo} ="App-logo" ="logo" /><p>Stripe Checkout - ReactJS</p><StripeBtn /></header></div>);}} className className src className alt export default App; Head to your browser and checkout your new Stripe component that can be reused anywhere on your project. Check out some screenshots below. Clicking the button on the left will make the modal appear on the right. Backend/Server Setup Now for our server… the backend. This is where a lot of people start to get nervous. But don’t worry, I am going to make this a painless and easy as possible. Remember our backend is simply receiving the token from the front end and sending it to stripe to complete the payment. Start by navigating to the root of your project in the terminal and run the following commands. mkdir servercd servertouch server.js yarn init -y yarn add express stripe cors dotenv Inside the server directory we create an index and initialize a yarn project. Setting the flag uses the defaults for the project. We then installed some packages we will need like we did in the front end. -y Next we will create a file that will hold our environment variables. You will want to put in your file. This is so we are not uploading our sensitive information like API keys to Github or having them available to the public. We will also create a new a directory and two new files inside there. .env .env .gitignore routes touch .env mkdir routescd routestouch index.js payment.js Inside the file add . Make sure you use your secret key from the sidebar your dashboard(Developers > API Keys). Let’s create the base of your server in that will be created with Express. Get the code below. .env STRIPE_SECRET_KEY="YOUR SECRET KEY HERE" /server/servers.js Create Your Server const express = require("express");const cors = require("cors");const bodyParser = require("body-parser");const dotenv = require("dotenv"); dotenv.config() const app = express(); app.use(bodyParser.json()); app.use(bodyParser.urlencoded({ extended: true })); app.use(cors()); const configureRoutes = require("./routes") configureRoutes(app); app.listen(8000, error => {if (error) throw error;console.log("Server running on port " + 8000);}); Above we import express to create an app/server. Import and configure to use our environment variables( ). Apply to the app and configure the app with our routes directory. Last step is have your app listen on local server 8000. Now we need to create our endpoints. Copy and paste the code below to get started. dotenv .env cors /routes/payments.js Payment Endpoints const stripe = require("stripe")(process.env.STRIPE_SECRET_KEY); const stripeChargeCallback = res => (stripeErr, stripeRes) => {if (stripeErr) {res.status(500).send({ error: stripeErr });} else {res.status(200).send({ success: stripeRes });}}; const paymentApi = app => {app.get("/", (req, res) => {res.send({message: "Hello Stripe checkout server!",timestamp: new Date().toISOString()});}); app.post("/", (req, res) => {const body = {source: req.body.token.id,amount: req.body.amount,currency: "usd"};stripe.charges.create(body, stripeChargeCallback(res));}); return app;}; module.exports = paymentApi; At the top we create a instance by passing in our from the .env file. Then created a callback that will send a response or error back to front end. Next we will create the endpoints(get, post, etc.) for the payment route. The get request is just your server up and running endpoint. This is whereThe post request creates a body of the token id, amount, and currency. We use our instance to creates a charge by passing in the object from the client and the callback for the response. This will finalize the purchase and charge the customer once. If you’re looking for a subscription or recurring billing, check out my other post. stripe STRIPE_SECRET_KEY stripe body Last step is going to be to connect your and the . This has already been configured in so simple add in the below code. server.js routes server.js /routes/index.js const paymentApi = require("./payment"); const configureRoutes = app => {paymentApi(app);}; module.exports = configureRoutes; You Made It That is it. In a terminal into and run . This will run the server in local host 8000. Go back to your client in your browser and give your new button a try. Here are a couple cards you can try: cd /server yarn start Visa: 4242 4242 4242 4242 — Exp: 01/20 — CVV: 123 Mastercard: 5555 5555 5555 4444 — Exp: 01/20 — CVV: 123 If you run into any issues please message me and I will do my best to help you out. If you enjoyed this, please share and follow me on and . Keep an eye out for future articles like Stripe subscription charges and more. Have an awesome day! Github Twitter

Stripe API, ReactJS, and Express

Blockchain in Healthcare: Opportunities, Challenges, and Applications

Monitoring your system is required. It helps you any issues before they cause any major downtime that effect your customers and damage your business reputation. It helps you also to based on the real usage of your system. But collecting metrics from different data sources isn’t enough, you need to your monitoring to meet your own business needs and define the right alerts so that any abnormal changes in the system will reported. detect plan growth personalize In this post, I will show you how to setup a resilient continuous monitoring platform with only open source projects & how to define an event alert to report changes in the system. Clone the following Github repository: git clone https://github.com/mlabouardy/terraform-aws-labs.git 1 — Terraform & AWS In the directory, update the file with your own credentials (make sure you have the right policies) : tick-stack/terraform variables.tfvars AWS IAM region = “AWS REGION” access_key = “YOUR AWS ACCESS KEY ID” secret_key = “YOUR AWS SECRET KEY” key_name = “YOUR SSH KEY PAIR” Issue the following command to download the AWS provider plugin: terraform init Issue the following command to provision the infrastructure: terraform apply — var-file=variables.tfvars 2 — Ansible & Docker Update the file with your instance DNS name: inventory [servers] ec2–52–206–156–244.compute-1.amazonaws.com Then, install the Ansible custom role: ansible-galaxy install mlabouardy.tick Execute the : Ansible Playbook ansible-playbook — private-key=aws.pem -i inventory playbook.yml Point your browser to , you should see : http://DNS_NAME:8083 InfluxDB Admin Dashboard Now, create an in ( ): InfluxDB Data Source Chronograf http://DNS_NAME:8888 Create a new Dashboard as follow: You can create multiple graphs to visualize different types of metrics: Note: For in depth details on how to create interactive & dynamic dashboards in check . Chronograf my previous tutorial You need to elaborate on the data collected to do something like alerting. So make sure to enable : Kapacitor Define a new alert to send a notification if the is higher than . Slack CPU utilization 70% To test it out, we need to generate some workload. For this case, I used : stress apt-get install stress Stressing the CPU: stress — cpu 4 — timeout 20s After few seconds, you should receive a notification. Slack

Continuous Monitoring with TICK stack

The global metaverse market has the potential to generate up to in value by 2030. The recent rebranding of Facebook to Meta and growing involvement by fashion houses like and has led to “Metaverse” becoming a buzzword and dominating the news over the past year. US$5 Trillion Gucci Balenciaga The Metaverse is generally defined as a network of immersive virtual worlds where people can work, interact socially and enjoy various experiences in digital environments that resemble the real world. Think of it as a giant video game or social platform where you can create an avatar, explore virtual spaces, socialize with other people, play games, attend events, and even buy and sell virtual goods and services. Currently, the metaverse is quite siloed, with different virtual worlds or platforms operating independently of each other. For example, if you create an avatar in one metaverse platform, you may not be able to use that same avatar in another platform, and you may have to start over from scratch. As the metaverse continues to expand, there will be a greater need for more interoperability between these virtual worlds so that users can seamlessly transfer their virtual assets from one world to another. In the panel below, our speakers share their views on how oracles will eventually be the bridge between all virtual worlds. https://youtu.be/vYcha56VMGw?embedable=true Before diving into the panel discussion, here are some significant concepts to note. Oracles And The Metaverse The term ‘Metaverse’ was coined by Neal Stephenson in 1992 to describe a virtual world that closely simulated reality. Since then, the Metaverse has been associated with gaming and entertainment. However, recent advancements in virtual and augmented reality have changed this notion, and now the concept of the metaverse has the potential to impact several other real-world sectors, including: Virtual classrooms and online learning tools could become more interactive and engaging within the metaverse, offering students new ways to learn and collaborate with each other. Education: The metaverse could enable new forms of e-commerce, such as virtual storefronts or virtual marketplaces for buying and selling digital goods and services. Commerce: Virtual real estate could become a new asset class, with people buying and selling virtual land, buildings, and other digital properties within the metaverse. The metaverse could provide new ways for people to connect and socialize with each other, from virtual parties to online dating. These are just a few examples of how the metaverse could impact different sectors in the real world. As the metaverse continues to evolve, we are likely to see new use cases emerge as well. Real estate: Social interactions: Undoubtedly, the Metaverse has immense potential, but there’s still something missing. With the rise of decentralised technologies and oracle networks, a metaverse economy that’s trustless and fully interoperable isn’t far behind. Oracles are third-party services that verify real-world data on the blockchain. They also allow different blockchain networks to communicate with each other by exchanging data. In the context of the metaverse, oracles can help facilitate interoperability between different virtual worlds or platforms. With the integration of oracles, users in the Metaverse will enjoy greater connectivity between previously siloed virtual worlds. Virtual assets may be migrated from one world to another and traded in various ways. Avatar identities can be integrated across several different platforms. Oracles can also help enable cross-platform transactions, such as buying and selling virtual assets or currency. By connecting different blockchain networks, oracles can ensure that transactions are secure, transparent, and consistent across different platforms. Overall, oracles can play a critical role in enabling interoperability in the metaverse, helping to create a more seamless and connected virtual world. Ethereum Virtual Machine (EVM) The e is a piece of software which executes all smart contracts and transactions on the Ethereum blockchain. It is often described as a virtual computer that sits on top of Ethereum’s hardware and node network layer. The EVM is Turing-complete, allowing developers to easily create custom smart contracts and decentralized applications in the Solidity programming language. In addition, smart contracts deployed on EVM-compatible chains like Polygon or Avalanche are recognized by Ethereum nodes, and developers can seamlessly transfer their dApps or tokens from Ethereum to these chains. Ethereum Virtual Machin Primitives are also referred to as cryptographic primitives, and they are the basic building blocks for securing data. Primitives are essential building blocks for creating secure cryptographic systems and protocols. Primitives Primitives can include: Algorithms that take input data of any size and produce a fixed-size output called a hash. Hash functions are commonly used in blockchain technology to ensure data integrity and to provide a way to securely store passwords. Hash functions: This is a type of encryption where the same key is used for both encryption and decryption. Symmetric key encryption is often used for securing data in transit, such as when sending data over the internet. Symmetric key encryption: **Public key encryption:**This is a type of encryption where two keys are used: one for encryption and one for decryption. The public key can be shared with anyone, while the private key is kept secret. Public key encryption is commonly used in digital signatures and secure communication protocols. These are cryptographic protocols used to verify the authenticity and integrity of digital documents or transactions. Digital signatures use a combination of public key encryption and hash functions to ensure that a document or transaction has not been tampered with. Digital signatures: Scaling Solutions And Rollups Scaling solutions refer to the methods implemented on blockchains, like Ethereum and Bitcoin, to improve transaction processing speed. These methods include on-chain scaling, such as or , such as rollups and state channels. Layer 1 sharding layer 2 scaling Rollups are layer 2 protocols which process transactions separately from the main network and then batch them to Layer 1, where consensus is reached. There are two types, namely optimistic and Zero-Knowledge rollups, which help improve speed and lower cost.  The ultimate goal of these solutions is to improve network scalability without sacrificing security or decentralization. This gives a detailed explanation of the different scaling solutions. article Consensus Mechanisms Consensus mechanisms refer to the protocols or algorithms which allow a network of nodes to agree on the state of a blockchain. These algorithms ensure the integrity of the network and protect it against . The most popular are Proof-of-Work (PoW), based on computational power exhausted and Proof-of-Stake (PoS), which depends on the amount of cryptocurrency held. Other examples of consensus mechanisms include Delegated Proof-of-Stake and Proof of Authority. Sybil attacks consensus mechanisms Permissionless Bridges VS Oracles Permissionless bridges are also referred to as trustless or . They connect two separate blockchain networks, allowing them to communicate and exchange data and assets. Bridges create interoperability between otherwise siloed networks without affecting their unique protocols or security models. cross-chain bridges The main difference between blockchain bridges and oracle networks is that  bridges connect different chains while oracles connect on-chain networks to real-world data. Both bridges increase functionalities for users on the blockchain by providing access to off-chain or non-native data and assets. Our Panelists Connor Martin, Protocol Lead, Medallion (Ex-Uniswap) Connor Martin has over six years of experience in the blockchain industry. In 2020, he began working at Uniswap Labs as an Integrations, Partnerships & Research lead. His work included  the development of Uniswap’s V3 oracle library. He also worked at Zerion as a Smart Contract Developer. Connor is now Protocol Lead at Medallion,  a music-focused crypto startup. Uniswap Website Medallion Website Connor Martin Twitter Rikard Hjort, Sr Formal Verification Engineer, Runtime Verification Rikard Hjort is researching formal methods for developing high-assurance smart contracts for blockchains. He worked on formalizing WebAssembly in K, and now uses KWasm to verify smart contracts written in WebAssembly. He has an M.Sc. in Computer Science from the Chalmers University of Technology, Sweden. He was an intern at Google in 2016 and 2017, and studied at the University of Tokyo in 2017-2018 where he combined his research on blockchains with studying coercion-resistant voting protocols. Runtime Verification Website Rikard Hjort Twitter Alexandra Dinh, Head of Marketing, Blockrocket At the time of recording, Alexandra was Head of Marketing at Blockrocket. As the Head of Marketing, Alexandra’s job was to spread the word about Blockrocket and their portfolio companies in the Blockchain community. She is now a Startup Mentor at Techstars and EY Startup Academy. Blockrocket Website Techstars Website Alexandra Dinh Twitter Paul Claudius, Co-founder, DIA Paul is a serial entrepreneur and crypto investor. Previously, he was Director Europe of the nu3 group based in Berlin, transforming the multi-million e-commerce business into a vertically integrated brand. Paul started his professional career as part of BNP Paribas Corporate Development in New York City and AXA Private Equity in Frankfurt am Main. Paul has advised and invested in multiple start-ups in health tech, IOT and e-commerce. At DIA, he manages the business development and the strategic partnerships. DIA Website Paul Claudius Twitter

SECRET KEY LABS

secretkeylabs.com

11-50 employees

Since 2021

COMPANY RANKING

SECRET KEY LABS

EVERGREEN INDEX #9990

Representing this company? Click here to claim and customize this page!

Secret Key Labs WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

SECRET KEY LABS

secretkeylabs.com

11-50 employees

Since 2021

COMPANY RANKING

SECRET KEY LABS

EVERGREEN INDEX #9990

RELATED COMPANIESRANK

STORIES ABOUT SECRET KEY LABS

Representing this company? Click here to claim and customize this page!

Secret Key Labs WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!