# PoS Published articles for PoS. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Mobile App Security in the Age of SoftPOS | Guardsquare DevFeed: [Mobile App Security in the Age of SoftPOS | Guardsquare]() Original publisher: [Read original article]() Author: Guardsquare Published: 2026-07-07T11:42:02Z Content type: article Language: en Sources: [Guardsquare Blog]() Topics: [Mobile](), [Mobile Security](), [Security](), [App](), [API](), [Exploit](), [SDKs](), [Malware]() Tags: [android](), [api](), [compliance](), [credentials](), [devices](), [exploit](), [financial-services](), [integrity](), [ios](), [malware](), [mobile](), [payment](), [payments](), [pos](), [protection](), [sdks](), [security](), [smartphone](), [thought-leadership]() ### AI overview This article examines the security implications of SoftPOS, which turns smartphones into card-present payment terminals. It explains that moving payment functions to mobile devices shifts responsibility to the device, operating system, application integrity, APIs, and runtime environment, and discusses threats including app tampering, reverse engineering, API abuse, credential theft, malware, and bypassed environment checks. ### Source excerpt As retailers look for faster, more flexible ways to accept payments, SoftPOS is becoming a cornerstone of modern payment strategies. It's expected that by 2027, more than 34.5 million merchants will accept payments through SoftPOS technology. The ability to turn any smartphone into a card-present terminal reduces hardware costs, simplifies onboarding, and supports new use cases like curbside, pop-up stores, and in-aisle checkout. ## Ultimate Go: Advanced Engineering Episode 7 DevFeed: [Ultimate Go: Advanced Engineering Episode 7]() Original publisher: [Read original article]() Published: 2022-12-19T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Databases](), [Data structures](), [Algorithms]() Tags: [2](), [audits](), [batch](), [batch-insert](), [bulk-upload](), [caching](), [consensus](), [consensus-algorithm](), [data-structures](), [databases](), [distributed](), [efficiency](), [engineering](), [go-blockchain](), [memory-pool](), [poa](), [pos](), [pow](), [proof-of-authority]() ### AI overview This video walkthrough explains how a proof-of-authority consensus mechanism affects a dependency manager's database throughput. It introduces a synchronized memory pool for queued records, reduces duplicate insertion work across nodes, and explains how batches of records become blockchain blocks and can be audited. ### Source excerpt Introduction In episode 6, Bill gives an overview of what consensus algorithms are and how these algorithms ensure distributed databases are in sync. Moving forward Bill will adopt the proof of authority (PoA) algorithm as a means to determine which node has the ability to write the next record. To jog your memory, PoA is a consensus mechanism where identity is used as a stake. By implementing this algorithm, Bill will add transparency to his dependency manager as he is no longer the only user with the ability to add new records. The dependency manager now meets the teams' requirements for transparency, however, it will have low throughput since only one record can be shared and inserted at a time. ## Ultimate Go Episode 6: Blockchain Consensus Algorithms DevFeed: [Ultimate Go Episode 6: Blockchain Consensus Algorithms]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Algorithms](), [Security](), [data]() Tags: [algorithms](), [blockchain](), [consensus](), [consensus-algorithm](), [distributed](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work](), [security]() ### AI overview This video explains why proof of work can be inefficient as a blockchain grows, focusing on duplicated computation and energy consumption. It introduces proof of stake and proof of authority as alternative consensus algorithms and discusses their role in maintaining valid data in a distributed database. ### Source excerpt Introduction In the last video, Bill left off talking about proof of work (PoW) algorithms. In a distributed and decentralized environment, PoW used to be the gold standard for a node to participate equitably in a Blockchain. However, with PoW as the number of nodes on the Blockchain increases, the amount of energy waste increases. This is because each node is performing the same computationally heavy calculation and only one node's energy usage is leveraged to write the next block. ## Ultimate Go: Advanced Engineering Episode 5 DevFeed: [Ultimate Go: Advanced Engineering Episode 5]() Original publisher: [Read original article]() Published: 2022-12-16T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Blockchain](), [Databases](), [Replication]() Tags: [atomic](), [consensus](), [consensus-algorithm](), [cryptographically-auditable](), [database](), [distributed](), [engineering](), [go-blockchain](), [golang-blockchain](), [poa](), [pos](), [pow](), [proof-of-authority](), [proof-of-work]() ### AI overview This video explains how to use blockchain concepts to design a distributed, auditable, synchronized, and scalable database for a dependency manager. It focuses on atomic writes, consensus, and a proof-of-work algorithm, while also discussing the inefficiency of proof of work and the emergence of proof of stake and proof of authority. ### Source excerpt Introduction In case you missed episode 4, Bill attempted to integrate current database sharing solutions to solve the "database ownership" problem his dependency manager faces. He tried providing copies of the database, implementing a load balancer and replication. While performing these experiments, Bill identified the qualities his dependency manager's database needs to have for users to trust it. He closed episode 4 by stating that his dependency manager needs a database that is distributed, cryptographically auditable, synchronized and scalable. By implementing this Bill hoped to provide greater transparency for his dependency manager. ## Amphora Workshop Advances Ethereum's Transition to Proof of Stake DevFeed: [Amphora Workshop Advances Ethereum's Transition to Proof of Stake]() Original publisher: [Read original article]() Author: Tim Beiko Published: 2021-10-15T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Hackathon](), [Development](), [Testing]() Tags: [api](), [architecture](), [ethereum](), [hackathon](), [pos](), [pow](), [research-development](), [testing]() ### AI overview The Amphora workshop brought Ethereum execution- and consensus-layer client teams together to resolve specification issues and reach milestones toward The Merge. The milestones progressed from implementing the merge specification to increasingly complex devnets and PoW-to-PoS transition testing. ### Source excerpt Earlier this year, the Rayonism hackathon kicked off to protoype the architecture for Ethereum's transition to proof of stake. The transition, often refered to as The Merge, will keep the existing beacon chain (eth2) and execution layer (eth1) clients, and "merge" both chains by making the beacon chain drive the... ## Finalized No. 25: Rayonism, blst Security Advisory, and Beacon Chain Security RfP DevFeed: [Finalized No. 25: Rayonism, blst Security Advisory, and Beacon Chain Security RfP]() Original publisher: [Read original article]() Author: Danny Ryan Published: 2021-04-02T00:00:00Z Content type: news Language: en Sources: [Ethereum Foundation Blog]() Topics: [Security](), [Development](), [Fuzzing/Fuzz testing](), [Testing](), [migration](), [Formal verification]() Tags: [discord](), [formal-verification](), [fuzzing](), [migration](), [pos](), [pow](), [research-development](), [security](), [testing]() ### AI overview This Ethereum Foundation update covers Rayonism Merge devnets, a patched security issue in the blst BLS library, and a request for proposals on Beacon Chain security and testing. ### Source excerpt tl;dr Rayonism☀, hacking the Merge together blst security advisory Reminder! Beacon Chain security+testing RfP... ## The Corner Round-up June 2020 DevFeed: [The Corner Round-up June 2020]() Original publisher: [Read original article]() Author: Richard Moot Published: 2020-06-30T22:59:20Z Content type: article Language: en Sources: [Square Corner Blog - Medium]() Topics: [API](), [Dependency injection](), [Compiler](), [Dagger](), [Kubernetes]() Tags: [api](), [apis](), [cloud](), [compiler](), [dagger](), [dagger-2](), [dependency-injection](), [kubernetes](), [payments](), [pos](), [security]() ### AI overview The Corner Round-up June 2020 recaps selected publications from Square's developer blog. It covers the Square Team API, the Hephaestus open source compiler plugin for Dagger 2, API Explorer's move from beta to general availability, Kubernetes pod security guidance, Loyalty and Customers APIs, and the Square Terminal API beta. ### Source excerpt In order to keep some of the followers still here on Medium, we wanted to provide a quick recap on some of the things that have been published over at The Corner Blog's new home https://developer.squareup.com/blog (in case you didn't know that already). We'll just be doing a quick summary of each new thing, but you can check out each topic in detail over at our new home. Manage Team Data from Any Platform with Square Team API We released a new Team API to allow managing Team data from any platform. You can track and edit large volumes of team member data automatically and synchronize data with any third-party platform in real time! Introducing Hephaestus In order to make dependency injection with Dagger 2 easier, we had created Hephaestus. It is an open source compiler plugin that automatically merges Dagger modules and component interfaces to make development more enjoyable. API Explorer Moves to General Availability The Square Developer team also transitioned the API Explorer from Beta to GA, bringing with it a lot of improvements to make testing Square APIs much more enjoyable and easy. Kubernetes - Pod Security Policies The cloud team at Square also did a write-up that provides some useful guidance and examples for handling Pod Security in Kubernetes. Reward Customers Wherever They Shop with Loyalty API and Customers API Additionally, Square Loyalty now has an API to make providing rewards to customers on other platforms. Using the Customers API and Loyalty API in combination can allow any developer to create a great rewards system, no matter where their customers are. Announcing Square Terminal API Beta Finally, we also released Terminal API, which lets you programmatically take payments using Square Terminal. This API allows developers to connect Square Terminal, an all-in-one card payments device, to their custom-built POS systems, no matter which platforms or operating systems they're developed on. Now that isn't everything that we've published since you've ## Announcing Square Terminal API Beta DevFeed: [Announcing Square Terminal API Beta]() Original publisher: [Read original article]() Author: Leher Pathak Published: 2020-04-22T19:00:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [API](), [Web](), [Android](), [iOS]() Tags: [android](), [api](), [apis](), [apple](), [australia](), [availability](), [canada](), [connectivity](), [desktop](), [developer-community](), [documentation](), [ios](), [payments](), [pos](), [uk](), [us](), [web](), [webhooks]() ### AI overview Square is releasing its Terminal API in beta, allowing developers to connect Square Terminal payment devices to custom point-of-sale systems across iOS, Android, web, and desktop platforms. The beta supports contactless payments and is available to developers in the US, Canada, UK, and Australia. ### Source excerpt Enable contactless payments and limit person-to-person contact with Square Terminal, connected to any POS ## Eth2 Consensus Mechanisms: GHOST and LMD-GHOST Fork Choice DevFeed: [Eth2 Consensus Mechanisms: GHOST and LMD-GHOST Fork Choice]() Original publisher: [Read original article]() Author: Carl Beekhuizen Published: 2020-02-12T00:00:00Z Content type: tutorial Language: en Sources: [Ethereum Foundation Blog]() Topics: [Algorithm](), [Protocol (disambiguation)](), [Network](), [Latency]() Tags: [algorithm](), [consensus](), [distributed-system](), [latency](), [network](), [pos](), [protocol](), [research-development]() ### AI overview This article explains the consensus mechanisms behind eth2, focusing on GHOST and its proof-of-stake variant, Latest Message Driven GHOST (LMD-GHOST). It describes how LMD-GHOST uses each validator's latest vote to select the chain head and how GHOST can reduce attack effectiveness and chain reorganization depth under high network latency. ### Source excerpt Special thanks to Sacha Yves Saint-Leger & Danny Ryan for review. In this installment, we'll discuss the consensus mechanisms behind eth2. Eth2 has a novel approach to deciding which block is the head of the chain, along with which blocks are and are not a part of the chain.... ## Validated: Staking on eth2 #0 -- Beacon Chain, Sharding, and Validator Roles DevFeed: [Validated: Staking on eth2 #0 -- Beacon Chain, Sharding, and Validator Roles]() Original publisher: [Read original article]() Author: Carl Beekhuizen Published: 2019-11-27T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Architecture & Design](), [Scalability](), [Security](), [systems]() Tags: [platform](), [pos](), [research-development](), [scalability](), [security](), [sharding]() ### AI overview This article introduces eth2 and explains the validator-focused role of its beacon chain. It describes the phased design: Phase 0 manages validators and shard coordination, Phase 1 adds shard data, and Phase 2 adds execution to create a decentralized computing platform. ### Source excerpt Thanks to Danny and Joe for review. As the launch of the beacon chain grows nearer and eth2 becomes ever more final, the time has come to fast-sync the community with the latest on the inner workings of eth2 and on the concrete requirements, incentives and experience of being... ## Creating a personalized, professional ticketing experience for any business, powered by Square APIs DevFeed: [Creating a personalized, professional ticketing experience for any business, powered by Square APIs]() Original publisher: [Read original article]() Author: Marisa Almeida Published: 2017-11-27T19:48:32Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [API](), [OAuth](), [Website]() Tags: [api](), [apis](), [e-commerce](), [integration](), [oauth](), [onboarding](), [payments](), [platform](), [pos]() ### AI overview The article profiles SimpleTix, a personalized event-ticketing platform that integrates Square's E-commerce API. It describes the platform's branded event pages, custom seating charts, OAuth onboarding, online and in-person ticket sales, and use of Square's multi-party settlement feature. ### Source excerpt SimpleTix is growing their platform through a differentiated experience and leveraging the new multi-party settlement feature through Square's E-commerce API. ## An Open Source Mining Pool Bounty and DEVgrant DevFeed: [An Open Source Mining Pool Bounty and DEVgrant]() Original publisher: [Read original article]() Author: Wendell Davis Published: 2016-03-29T09:05:02Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Open Source](), [Software]() Tags: [bounty](), [ethereum](), [network](), [open-source](), [pos](), [pow](), [research-development]() ### AI overview The Ethereum Foundation proposes a bounty for open-source Ethereum mining pool software to improve mining decentralization and reduce the efficiency gap with proprietary alternatives. The bounty offers up to 100 ETH per percentage point of adopted hashpower, subject to stated caps, plus a $10,000 DEVgrants contribution once development begins. ### Source excerpt Ethereum's present reliance on Proof of Work (PoW) mining is not ideal, and while we continue to work with gusto towards a Proof of Stake solution (PoS), we have to live with PoW as gracefully as possible (at least until the eventual switch!). Meanwhile, in the interest of overall network... ## Integrating Node.js with a C# dll DevFeed: [Integrating Node.js with a C# dll]() Original publisher: [Read original article]() Published: 2014-03-30T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [C#](), [Node.js](), [Process](), [API](), [JSON]() Tags: [c-sharp](), [console](), [json](), [node-js](), [payments](), [pos](), [process](), [rest-api](), [server](), [web-app]() ### AI overview This article describes integrating a Node.js server application with a C# DLL used to control a POS payment terminal. It presents Edge.js as one option and process invocation through Node.js as another, including communication through process arguments and STDOUT/STDIN, with JSON suggested for structured responses. ### Source excerpt Lorem ipsum dolor sit amet ## Use cases for ReactOS DevFeed: [Use cases for ReactOS]() Original publisher: [Read original article]() Published: 2013-05-26T00:00:00Z Content type: opinion Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Windows](), [win32](), [networking](), [Cloud]() Tags: [free](), [networking](), [open-source](), [os](), [pos](), [react](), [reactos](), [remote](), [thin-client](), [win32](), [winapi](), [windows]() ### AI overview This article examines business-oriented use cases for ReactOS, including remote desktop thin clients, point-of-sale and industrial systems, and remotely hosted applications. It argues that these narrower scenarios may be more attainable than replacing Windows XP or serving as a general-purpose Windows successor. ### Source excerpt Many people see ReactOS as a Windows XP successor, a way for them to avoid the changes Microsoft brought about in Windows 8. This is a somewhat idealized goal, as ReactOS would need to be much more complete before it could attempt to fill in that role. There are however other use cases for which ReactOS is much closer to being ready for. Many of these however are more business use cases than consumer use cases.