N) Hashing

As a work is created on RNDR, its corresponding ORBX scene graph is hashed. This hash represents a unique identifier for what is inside the ORBX that cannot be reverse-engineered or duplicated by a different scene. With all assets and work hashed on the network, completion of render jobs can be codified and tracked - for example the releasing of a confirmed and paid render from its watermarked state to a creator. With the hashing of all assets on the network, RNDR provides traceability and attribution needed for deep chain of authorship. Through a RNDR API, complex applications can be developed that leverage hashed assets with unique identifiers.


The RNDR network provides an open API, enabling users to build custom applications on top of RNDR. The API supports customizable asset rendering pipelines, for example swapping specific files like .OCS textures on RNDR, rather than re-uploading complete ORBX files. This enables users to build new micro-services and applications on top of RNDR. Further the RNDR API provides developers with access to a templated UI that they can customize to their workflow needs. Using the RNDR API, administrators can create AUTH permissions for multiple users in a shared studio, with credential management tools for uploading scenes and submitting jobs. As a result, a studio can customize their account administration.
Last modified 3yr ago