The document is a summary of a smart contract security audit conducted by TechRate on the Parallax smart contracts. The audit found no issues of high or medium severity. Some low level issues were identified related to owner privileges, but these would not be considered security vulnerabilities. The audit scope did not include analysis of any applications or operations, and only reviewed the provided smart contracts. In conclusion, the smart contracts were found to not contain any high severity issues, but the liquidity pair contract and liquidity locking details were not fully reviewed.
This is the updated factsheet for the Trakx Bitcoin Control15 CTI. Trakx.io offers investment products that tracks digital assets. Trakx Bitcoin Control15 gets an exposure to the Bitcoin with a volatility control mechanism, in order to maintain the
volatility around 15%.
Dreamforce '23 - Master the Art of Becoming a Salesforce Security NinjaAlesia Dvorkina
Discover expert strategies, best practices, and tools to safeguard your Salesforce org. Elevate your security expertise and become a true guardian of your Salesforce galaxy.
This the the formal version 1.0 of the DDS Security specification released September 2016. OMG document number formal/2016-08-01.
DDS-Security defines the Security Model and Service Plugin Interface (SPI) architecture for compliant DDS implementations.
The DDS Security Model is enforced by the invocation of these SPIs by the DDS implementation. This specification also defines a set of builtin implementations of these SPIs.
* The specified builtin SPI implementations enable out-of-the box security and interoperability between compliant DDS applications.
* The use of SPIs allows DDS users to customize the behavior and technologies that the DDS implementations use for Information Assurance, specifically customization of Authentication, Access Control, Encryption, Message Authentication, Digital Signing, Logging and Data Tagging.
This instrument is designed to replicate the performance of the 10 leading Digital Assets on the ethereum blockchain, also called ERC20 token. The index represents token from both centralised exchanges and Decentralised Finance (DeFi).
Top 10 Ethereum replicates the performance of the 10 leading digital assets on the Ethereum blockchain. Among those, centralised exchanges token weight the most.
NOTE: This document has been obsoleted by the Adopted DDS Specification
OMG DDS Security Draft Specification. This is the 5th Revised Submission to the DDS Security Specification.
Also accessible from the OMG at:
http://www.omg.org/members/cgi-bin/doc?mars/13-05-17.pdf
The OMG Application Instrumentation Specification provides a simple way to instrument applications so that their internal state can be accessed by remote applications and tools in order to supervise the correct operation of the system. All this with minimal impact on the application so that it can be used even within real-time threads. The Application Instrumentation API is available in C and Java.
This specification was adopted (in Beta form) by the OMG in September 2013
This is the updated factsheet for the Trakx Bitcoin Control15 CTI. Trakx.io offers investment products that tracks digital assets. Trakx Bitcoin Control15 gets an exposure to the Bitcoin with a volatility control mechanism, in order to maintain the
volatility around 15%.
Dreamforce '23 - Master the Art of Becoming a Salesforce Security NinjaAlesia Dvorkina
Discover expert strategies, best practices, and tools to safeguard your Salesforce org. Elevate your security expertise and become a true guardian of your Salesforce galaxy.
This the the formal version 1.0 of the DDS Security specification released September 2016. OMG document number formal/2016-08-01.
DDS-Security defines the Security Model and Service Plugin Interface (SPI) architecture for compliant DDS implementations.
The DDS Security Model is enforced by the invocation of these SPIs by the DDS implementation. This specification also defines a set of builtin implementations of these SPIs.
* The specified builtin SPI implementations enable out-of-the box security and interoperability between compliant DDS applications.
* The use of SPIs allows DDS users to customize the behavior and technologies that the DDS implementations use for Information Assurance, specifically customization of Authentication, Access Control, Encryption, Message Authentication, Digital Signing, Logging and Data Tagging.
This instrument is designed to replicate the performance of the 10 leading Digital Assets on the ethereum blockchain, also called ERC20 token. The index represents token from both centralised exchanges and Decentralised Finance (DeFi).
Top 10 Ethereum replicates the performance of the 10 leading digital assets on the Ethereum blockchain. Among those, centralised exchanges token weight the most.
NOTE: This document has been obsoleted by the Adopted DDS Specification
OMG DDS Security Draft Specification. This is the 5th Revised Submission to the DDS Security Specification.
Also accessible from the OMG at:
http://www.omg.org/members/cgi-bin/doc?mars/13-05-17.pdf
The OMG Application Instrumentation Specification provides a simple way to instrument applications so that their internal state can be accessed by remote applications and tools in order to supervise the correct operation of the system. All this with minimal impact on the application so that it can be used even within real-time threads. The Application Instrumentation API is available in C and Java.
This specification was adopted (in Beta form) by the OMG in September 2013
NOTE: This document has been obsoleted by the Adopted DDS Specification
This is the September 2013 Draft Submission to the OMG DDS Security Specification
This instrument uses a quantitative algorithm which finds an optimal basket with the lowest (1 year) correlation to the standard 6040 portfolio composed of 60% ETF equities and 40% ETF bonds. The optimal basket is rebalanced every month, picking 3 to 5 digital assets among 100 biggest market capitalisations of both coinbase custody and Ethereum ERC20 universes.
This is the DDS-XRCE 1.0 Beta specification adopted by the OMG March 2018.
The purpose of DDS-XRCE is to enable resource-constrained devices to participate in DDS communication, while at the same time allowing those devices to be disconnected for long periods of time but still be discoverable by other DDS applications.
DDS-XRCE defines a wire protocol, the DDS-XRCE protocol, to be used between an XRCE Client and XRCE Agent. The XRCE Agent is a DDS Participant in the DDS Global Data Space. The DDS-XRCE protocol allows the client to use the XRCE Agent as a proxy in order to produce and consume data in the DDS Global Data Space.
This instrument is designed to replicate the performance of the 10 leading Decentralised Finance ("DeFi") tokens available on Ethereum. DeFi provides a digital alternative to the entire traditional financial services, not only payments but also loans, savings, trading, or insurance, accessible to anyone in the world with an internet connection. Most of the applications of DeFi involve the creation and execution of smart contracts, computer programs intended to be automatically executed on the blockchain when the conditions of the contract are met. Decentralised Finance aims at disintermediating and reducing transaction costs.
This is the DDS Security adopted specification.
It was adopted as an OMG standard in June 2014.
The official URL is http://www.omg.org/spec/DDS-SECURITY/
This specification is a response to the OMG RFP "eXtremely Resource Constrained Environments DDS (DDS- XRCE)"
It defines a DDS-XRCE Service based on a client-server protocol between a resource constrained, low-powered device (client) and an Agent (the server) that enables the device to communicate with a DDS network and publish and subscribe to topics in a DDS domain. The specifications purpose and scope is to ensure that applications based on different vendor’ implementations of the DDS-XRCE Service are compatible and interoperable.
This is the Joint submission by RTI, TwinOaks, and eProsima. Updated September 2017, OMG document number mars/2017-09-18.
Overview of a Reinsurance Smart Contract Deployment on a Private or Public Ethereum Blockchain. This project was created and on the Nivaura Financial Instrument Issuance and Administration Engine.
Pulsar Summit Asia 2022 - Keeping on top of hybrid cloud usage with PulsarShivji Kumar Jha
This presentation will cover how we force controls on an application over a hybrid cloud infrastructure built from a combination of different clouds that could include private and public clouds. For instance, you could deploy your microservice in AWS but use BigTable as your data store.
Every cloud or on-premise infrastructure provider provides monitoring, alerting, metering, audit trail etc. In a hybrid cloud use case, the IT team needs a single view of the usage across the cloud providers. Such a platform needs to combine the data sourcing of these utilities from different infrastructure providers, parse them into a common format and build an integrated data sink. Adding to it the challenge of each data source evolving its data formats, volume, velocity, throughput, latency etc. You have a challenging task to understand data from varied sources and present it in one view.
We will present an architecture that has been battle-tested in production for over five years. The components include Pulsar, Flink, PostgreSQL, Redis, Neo4J DB, rule/ML engine etc., to name a few technologies.
After this presentation, you will learn more about
1. Combining infrastructure from multiple clouds and on-premise providers to build your application.
2. Appreciate the need for lambda architecture.
3. How to stream ever-evolving multi-schema data using pulsar
4. How to write custom rules over a stream analytics framework to make your application.
NOTE: This document has been obsoleted by the Adopted DDS Specification
OMG DDS Security Draft Specification. This is the 4th Revised Submission to the DDS Security Specification.
Also accessible from the OMG at:
http://www.omg.org/members/cgi-bin/doc?mars/13-02-15.pdf
PharmaLedger – Requirement document report for governance applicationPharmaLedger
This document provides requirements for PharmaLedger governance automation tools. The requirements emerged from prior work on PharmaLedger governance recommendations and other governance definition activities of the PharmaLedger project.
As PharmaLedger governance emerged as a highly complex topic that has organizational, business network, blockchain platform and use case aspects. Some of the PharmaLedger governance activities will be based on management by people through direct interpersonal communication (“human governance” as opposed to “automated governance”). Such activities were identified and placed outside the scope of this document, as they can be performed using commercial communication, remote meeting and project management tools.
Among other things, this document identifies governance areas that merit dedicated automation tools. Such areas include opinion polling, voting on structured and generic unstructured proposals, blockchain network management (including intra-organizational and shared inter-organizational blockchains) and use case specific decision making.
The requirements contained by this document are for tools that will assist, automate or semi-automate governance of PharmaLedger organization, business network, blockchain platform and use case applications. Since the implementation of use cases is not mature at the time of submission of this document, some of the use case governance requirements will be provided at a later stage of the project.
Further work on definition of governance automation features is expected to take place in an interactive fashion, based on the initial implementation of the PharmaLedger Governance Application (PLGapp) based on the present recommendation, followed by agile iterations involving end users.
This is the Beta 1 version of the OPC UA / DDS Gateway specification released by the Object Management Group in March 2018.
This specification defines a standard, vendor-independent, configurable gateway that enables interoperability and information exchange between systems that use DDS and systems that use OPC UA.
Data Distribution Service (DDS) is a family of standards from the Object Management Group (OMG) that provide connectivity, interoperability, and portability for Industrial Internet, cyber-physical, and mission-critical applications.
The DDS connectivity standards cover Publish-Subscribe (DDS), Service Invocation (DDS-RPC), Interoperability (DDS-RTPS), Information Modeling (DDS-XTYPES), Security (DDS-SECURITY), as well as programing APIs for C, C++, Java and other languages.
The OPC Unified Architecture (OPC UA) is an information exchange standard for Industrial Automation and related systems created by the OPC Foundation. The OPC UA standard provides an Addressing and Information Model for Data Access, Alarms, and Service invocation layered over multiple transport-level protocols such as Binary TCP and Web-Services.
DDS and OPC UA exhibit significant deployment similarities:
• Both enable independently developed applications to interoperate even when those applications come from different vendors, use different programming languages, or run on different platforms and operating systems.
• Both have significant traction within Industrial Automation systems.
• Both define standard protocols built on top of the TCP/ UDP/IP Internet stacks.
The two technologies may coexist within the same application domains; however, while there are solutions that bridge between DDS and OPC UA, these are based on custom mappings and cannot be relied to work across vendors and products.
Siyata Mobile (Siyata or the Company) is a leading developer and distributor of technologically advanced rugged smartphones, in-vehicle mounted IoT cellular communications devices, and cellular signal boosters for global first responders and enterprise customers based on Push-to-Talk Over Cellular (PoC) technology. Siyata’s PoC solutions operate over 4G LTE networks thus enabling subscribers to use their cellular phones as walkie-talkies with unlimited range and provides instant voice and video connectivity across the nation or internationally. Siyata markets its devices with tier one cellular carriers and distributors in the United States, Canada, Europe, Middle East, and Australia.
NOTE: This document has been obsoleted by the Adopted DDS Specification
This is the September 2013 Draft Submission to the OMG DDS Security Specification
This instrument uses a quantitative algorithm which finds an optimal basket with the lowest (1 year) correlation to the standard 6040 portfolio composed of 60% ETF equities and 40% ETF bonds. The optimal basket is rebalanced every month, picking 3 to 5 digital assets among 100 biggest market capitalisations of both coinbase custody and Ethereum ERC20 universes.
This is the DDS-XRCE 1.0 Beta specification adopted by the OMG March 2018.
The purpose of DDS-XRCE is to enable resource-constrained devices to participate in DDS communication, while at the same time allowing those devices to be disconnected for long periods of time but still be discoverable by other DDS applications.
DDS-XRCE defines a wire protocol, the DDS-XRCE protocol, to be used between an XRCE Client and XRCE Agent. The XRCE Agent is a DDS Participant in the DDS Global Data Space. The DDS-XRCE protocol allows the client to use the XRCE Agent as a proxy in order to produce and consume data in the DDS Global Data Space.
This instrument is designed to replicate the performance of the 10 leading Decentralised Finance ("DeFi") tokens available on Ethereum. DeFi provides a digital alternative to the entire traditional financial services, not only payments but also loans, savings, trading, or insurance, accessible to anyone in the world with an internet connection. Most of the applications of DeFi involve the creation and execution of smart contracts, computer programs intended to be automatically executed on the blockchain when the conditions of the contract are met. Decentralised Finance aims at disintermediating and reducing transaction costs.
This is the DDS Security adopted specification.
It was adopted as an OMG standard in June 2014.
The official URL is http://www.omg.org/spec/DDS-SECURITY/
This specification is a response to the OMG RFP "eXtremely Resource Constrained Environments DDS (DDS- XRCE)"
It defines a DDS-XRCE Service based on a client-server protocol between a resource constrained, low-powered device (client) and an Agent (the server) that enables the device to communicate with a DDS network and publish and subscribe to topics in a DDS domain. The specifications purpose and scope is to ensure that applications based on different vendor’ implementations of the DDS-XRCE Service are compatible and interoperable.
This is the Joint submission by RTI, TwinOaks, and eProsima. Updated September 2017, OMG document number mars/2017-09-18.
Overview of a Reinsurance Smart Contract Deployment on a Private or Public Ethereum Blockchain. This project was created and on the Nivaura Financial Instrument Issuance and Administration Engine.
Pulsar Summit Asia 2022 - Keeping on top of hybrid cloud usage with PulsarShivji Kumar Jha
This presentation will cover how we force controls on an application over a hybrid cloud infrastructure built from a combination of different clouds that could include private and public clouds. For instance, you could deploy your microservice in AWS but use BigTable as your data store.
Every cloud or on-premise infrastructure provider provides monitoring, alerting, metering, audit trail etc. In a hybrid cloud use case, the IT team needs a single view of the usage across the cloud providers. Such a platform needs to combine the data sourcing of these utilities from different infrastructure providers, parse them into a common format and build an integrated data sink. Adding to it the challenge of each data source evolving its data formats, volume, velocity, throughput, latency etc. You have a challenging task to understand data from varied sources and present it in one view.
We will present an architecture that has been battle-tested in production for over five years. The components include Pulsar, Flink, PostgreSQL, Redis, Neo4J DB, rule/ML engine etc., to name a few technologies.
After this presentation, you will learn more about
1. Combining infrastructure from multiple clouds and on-premise providers to build your application.
2. Appreciate the need for lambda architecture.
3. How to stream ever-evolving multi-schema data using pulsar
4. How to write custom rules over a stream analytics framework to make your application.
NOTE: This document has been obsoleted by the Adopted DDS Specification
OMG DDS Security Draft Specification. This is the 4th Revised Submission to the DDS Security Specification.
Also accessible from the OMG at:
http://www.omg.org/members/cgi-bin/doc?mars/13-02-15.pdf
PharmaLedger – Requirement document report for governance applicationPharmaLedger
This document provides requirements for PharmaLedger governance automation tools. The requirements emerged from prior work on PharmaLedger governance recommendations and other governance definition activities of the PharmaLedger project.
As PharmaLedger governance emerged as a highly complex topic that has organizational, business network, blockchain platform and use case aspects. Some of the PharmaLedger governance activities will be based on management by people through direct interpersonal communication (“human governance” as opposed to “automated governance”). Such activities were identified and placed outside the scope of this document, as they can be performed using commercial communication, remote meeting and project management tools.
Among other things, this document identifies governance areas that merit dedicated automation tools. Such areas include opinion polling, voting on structured and generic unstructured proposals, blockchain network management (including intra-organizational and shared inter-organizational blockchains) and use case specific decision making.
The requirements contained by this document are for tools that will assist, automate or semi-automate governance of PharmaLedger organization, business network, blockchain platform and use case applications. Since the implementation of use cases is not mature at the time of submission of this document, some of the use case governance requirements will be provided at a later stage of the project.
Further work on definition of governance automation features is expected to take place in an interactive fashion, based on the initial implementation of the PharmaLedger Governance Application (PLGapp) based on the present recommendation, followed by agile iterations involving end users.
This is the Beta 1 version of the OPC UA / DDS Gateway specification released by the Object Management Group in March 2018.
This specification defines a standard, vendor-independent, configurable gateway that enables interoperability and information exchange between systems that use DDS and systems that use OPC UA.
Data Distribution Service (DDS) is a family of standards from the Object Management Group (OMG) that provide connectivity, interoperability, and portability for Industrial Internet, cyber-physical, and mission-critical applications.
The DDS connectivity standards cover Publish-Subscribe (DDS), Service Invocation (DDS-RPC), Interoperability (DDS-RTPS), Information Modeling (DDS-XTYPES), Security (DDS-SECURITY), as well as programing APIs for C, C++, Java and other languages.
The OPC Unified Architecture (OPC UA) is an information exchange standard for Industrial Automation and related systems created by the OPC Foundation. The OPC UA standard provides an Addressing and Information Model for Data Access, Alarms, and Service invocation layered over multiple transport-level protocols such as Binary TCP and Web-Services.
DDS and OPC UA exhibit significant deployment similarities:
• Both enable independently developed applications to interoperate even when those applications come from different vendors, use different programming languages, or run on different platforms and operating systems.
• Both have significant traction within Industrial Automation systems.
• Both define standard protocols built on top of the TCP/ UDP/IP Internet stacks.
The two technologies may coexist within the same application domains; however, while there are solutions that bridge between DDS and OPC UA, these are based on custom mappings and cannot be relied to work across vendors and products.
Siyata Mobile (Siyata or the Company) is a leading developer and distributor of technologically advanced rugged smartphones, in-vehicle mounted IoT cellular communications devices, and cellular signal boosters for global first responders and enterprise customers based on Push-to-Talk Over Cellular (PoC) technology. Siyata’s PoC solutions operate over 4G LTE networks thus enabling subscribers to use their cellular phones as walkie-talkies with unlimited range and provides instant voice and video connectivity across the nation or internationally. Siyata markets its devices with tier one cellular carriers and distributors in the United States, Canada, Europe, Middle East, and Australia.
Similar to Parallax DeFi [PRLX] BSC BEP-20 | Techrate Final Audit (20)
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
2. Disclaimer
This is a limited report on our findings based on our analysis, in accordance with
good industry practice as at the date of this report, in relation to cybersecurity
vulnerabilities and issues in the framework and algorithms based on smart contracts,
the details of which are set out in this report. In order to get a full view of our
analysis, it is crucial for you to read the full report. While we have done our best in
conducting our analysis and producing this report, it is important to note that you
should not rely on this report and cannot claim against us on the basis of what it says
or doesn’t say, or how we produced it, and it is important for you to conduct your own
independent investigations before making any decisions. We go into more detail on
this in the below disclaimer below – please make sure to read it in full.
DISCLAIMER: By reading this report or any part of it, you agree to the terms of this
disclaimer. If you do not agree to the terms, then please immediately cease reading
this report, and delete and destroy any and all copies of this report downloaded
and/or printed by you. This report is provided for information purposes only and on a
non-reliance basis, and does not constitute investment advice. No one shall have any
right to rely on the report or its contents, and TechRate and its affiliates (including
holding companies, shareholders, subsidiaries, employees, directors, officers and
other representatives) (TechRate) owe no duty of care towards you or any other
person, nor does TechRate make any warranty or representation to any person on
the accuracy or completeness of the report. The report is provided "as is", without
any conditions, warranties or other terms of any kind except as set out in this
disclaimer, and TechRate hereby excludes all representations, warranties,
conditions and other terms (including, without limitation, the warranties implied by
law of satisfactory quality, fitness for purpose and the use of reasonable care and
skill) which, but for this clause, might have effect in relation to the report. Except and
only to the extent that it is prohibited by law, TechRate hereby excludes all liability
and responsibility, and neither you nor any other person shall have any claim against
TechRate, for any amount or kind of loss or damage that may result to you or any
other person (including without limitation, any direct, indirect, special, punitive,
consequential or pure economic loss or damages, or any loss of income, profits,
goodwill, data, contracts, use of money, or business interruption, and whether in
delict, tort (including without limitation negligence), contract, breach of statutory
duty, misrepresentation (whether innocent or negligent) or otherwise under any
claim of any nature whatsoever in any jurisdiction) in any way arising from or
connected with this report and the use, inability to use or the results of use of this
report, and any reliance on this report.
The analysis of the security is purely based on the smart contracts alone. No
applications or operations were reviewed for security. No product code has been
reviewed.
3. Background
TechRate was commissioned by Parallax to perform an audit of smart
contracts:
https://testnet.bscscan.com/address/0x70d2ace4f5c69b3298d92d85ffb6d274c1e88f
eb#code
The purpose of the audit was to achieve the following:
● Ensure that the smart contract functions as intended.
● Identify potential security issues with the smart contract.
The information in this report should be used to understand the risk exposure of the
smart contract, and as a guide to improve the security posture of the smart contract
by remediating the issues that were identified.
4. Issues Checking Status
Issue description Checking status
1. Compiler errors. Passed
2. Race conditions and Reentrancy. Cross-function race
conditions.
Passed
3. Possible delays in data delivery. Passed
4. Oracle calls. Passed
5. Front running. Passed
6. Timestamp dependence. Passed
7. Integer Overflow and Underflow. Passed
8. DoS with Revert. Passed
9. DoS with block gas limit. Passed
10. Methods execution permissions. Passed
11. Economy model of the contract. Passed
12. The impact of the exchange rate on the logic. Passed
13. Private user data leaks. Passed
14. Malicious Event log. Passed
15. Scoping and Declarations. Passed
16. Uninitialized storage pointers. Passed
17. Arithmetic accuracy. Passed
18. Design Logic. Passed
19. Cross-function race conditions. Passed
20. Safe Open Zeppelin contracts implementation and
usage.
Passed
21. Fallback function security. Passed
5. Security Issues
High Severity Issues
No high severity issues found.
Medium Severity Issues
No medium severity issues found.
Low Severity Issues
No low severity issues found.
Owner privileges (In the period when the owner is not
renounced)
• Owner can change _arrayLength value.
• Owner can enable trading.
• Owner can disable launchPhase.
• Owner can blacklist and authorize addresses.
• Owner can exclude from the fee.
• Owner can mark addresses as pairs.
• Owner can change fees.
• Owner can change triggerTokens value.
• Owner can enable/disable noFeeToTransfer.
• Owner can change the maximum transaction amount and maximum
wallet token.
• Owner can withdraw contract ERC20 tokens.
• Owner can change router and pair addresses.
6. Conclusion
Smart contracts do not contain high severity issues! Liquidity pair
contract’s security is not checked due to out of scope.
Liquidity locking details are NOT provided by the team.
TechRate note:
Please check the disclaimer above and note, the audit makes no
statements or warranties on business model, investment
attractiveness or code sustainability. The report is provided for the
only contract mentioned in the report and does not include any
other potential contracts deployed by Owner.