Enjoy brand new web3 UI for the objects tokenization:

https://wallet.3dpass.org/assets/objects

Check out this one: https://github.com/xchainw/p3d-db

The network has been upgraded at the block height of `1,422,643`.
The EVM compatibility layer has come into operation.

The network has been upgraded online at the block height of `1,422,643`

Upgrading to the v31: https://github.com/3Dpass/3DP/releases/tag/v31 is mandatory for every node to pass.

Enjoy brand new Mining and Validator dashboard!

Web: https://miner.p3d.top
Github: https://github.com/3Dpass/mining-leaderboard

EVM Compatibility Layer has been released.

Node v31
https://github.com/3Dpass/3DP/releases/tag/v31


Upgrade your nodes!

Correct, there is a consensus between the main block and L2 block in place to ensure 1:1 mapping.

In about 5 month or so. If you'd like to know for certain just ask deepWiki https://deepwiki.com/3Dpass/3DP

We are welcoming everyone to participate in public code review on the new version coming soon on mainnet.

New version description:

1. Frontier – EVM compatibility layer (https://github.com/polkadot-evm/frontier) - full integration of both the EVM executor and eth type blockchain emulator.

2. Precompiles (precompiled smart contracts):
 A. Standard Ethereum precompiles: https://github.com/3Dpass/3DP/tree/test/pallets/evm/precompile
 B. Custom precompiles (Solidity interfaces) for LoT runtime modules:
  - Native token P3Dt - balances-erc20 precompile: https://github.com/3Dpass/3DP/tree/test/precompiles/balances-erc20
  - Local assets 3DPRC2 - assets-erc20 precompile https://github.com/3Dpass/3DP/tree/test/precompiles/assets-erc20
  - Proxy module precompile https://github.com/3Dpass/3DP/tree/test/precompiles/proxy
  - Utils and batch calls precompiles

3. The Proxy runtime module which allows for one account to delegate certain calls to another account, so the calls can be executed on the delegator's behalf. https://github.com/paritytech/substrate/tree/master/frame/proxy

The source codes: https://github.com/3Dpass/3DP/tree/test

Looking forward to your feedback!

Happy to announce that mining is now available for Windows devices via Docker:

https://github.com/3Dpass/3DP?tab=readme-ov-file#node-and-mining-with-docker

P.S.: There had been some issues with docker scripts which have been solved with the latest fix: https://github.com/3Dpass/3DP/commit/ca38875cdc62549aef48a2c05d18035062eec8dc

New telemetry server came into operation!

Telemetry server: https://3dpass.network/

Use this flag to switch your Nodes to the server:

Brand new open source blockchain explorer came into operation and now available via https://3dpscan.xyz

It cannot. Would you like to explore why:  https://3dpass.org/features#ledger-why-1node-1vote

The EVM emulator feature testing period is getting started!

https://github.com/3Dpass/3DP/tree/test

Enjoy 3DPRC-2 tokens support on the web3 wallet: https://wallet.3dpass.org

- Tokens balances
- Tokens transfers

Guidelines: https://3dpass.org/assets#transfers

 

Sure, you can. Mining is accessible.

Enjoy new release on the mobile wallet!

v2.17.3
https://github.com/3Dpass/threedpass/releases/tag/v2.17.3


How to: https://3dpass.org/mobile-wallet
Play Store: https://play.google.com/store/apps/details?id=com.threedpass.wallet

The mainnet has been upgraded to the Node v28

https://github.com/3Dpass/3DP/releases/tag/v28

--

The upgrade description:

Validator set
- The `addSelf` method for Validator-candidates to join by themselves:
   - 10 000 P3D set up fee goes to Treasury
   - No block authorship requirements
- The Validator-candidates queue for both joining and rejoining ones:
   - Limit: 1 validator per session is allowed into the set
   - Council vote can bypass the queue
   - On-chain Identity min requirements: Reasonable


3DPRC-2
- The object max size is expanded to 1 Mb
- Estimation time limit is expanded to 30 sec
- Private/Public tag on putObject
- Minor fixes: https://github.com/3Dpass/3DP/issues/88

Identity
- The `suspend` and `resume` methods for registrars. Registrars can be suspended/resumed by the Council vote.

Hey everyone,

I've got some exciting news to share!

The latest release opened up the possibility for Validators to join freely: https://github.com/3Dpass/3DP/releases/tag/v28
Validators represent the second layer of Nodes in Proof of Scan: https://3dpass.org/features#scanproof-network-structure

--

Explore how to set up Validator: https://3dpass.org/mainnet#validator

Let me put my two cents in by answering the question 

It didn't work because the network must take ultimate responsibility for each and every block/asset on the blockchain, which neither of single nodes/individuals can take. And this could not be fulfilled without having the whole bunch of data (proofs included) sealed into the Merkle tree. So it becomes irrefutable evidence proved by math.

The bottom line is that if we want the network to take responsibility for the asset authenticity, it must be stored on the blockchain and sealed into the block header by the block author. https://3dpass.org/features#ledger-why-1node-1vote

And if the asset owner takes 100% responsibility himself (no guarantee for public), he can store the  object wherever he likes. Having the HASH ID (the object identity) stored on the blockchain would be enough in the case.

3Dpass consensus Proof of Scan is based on recognition function instead of regular hashing. So, the network is capable of the object properties processing and thus it can take responsibility for the object authenticity (not to mistake with the file authenticity). Which none of the existing L1 blockchain platforms can provide.