/** * REST API: WP_REST_Post_Statuses_Controller class * * @package WordPress * @subpackage REST_API * @since 4.7.0 */ /** * Core class used to access post statuses via the REST API. * * @since 4.7.0 * * @see WP_REST_Controller */ class WP_REST_Post_Statuses_Controller extends WP_REST_Controller { /** * Constructor. * * @since 4.7.0 */ public function __construct() { $this->namespace = 'wp/v2'; $this->rest_base = 'statuses'; } /** * Registers the routes for post statuses. * * @since 4.7.0 * * @see register_rest_route() */ public function register_routes() { register_rest_route( $this->namespace, '/' . $this->rest_base, array( array( 'methods' => WP_REST_Server::READABLE, 'callback' => array( $this, 'get_items' ), 'permission_callback' => array( $this, 'get_items_permissions_check' ), 'args' => $this->get_collection_params(), ), 'schema' => array( $this, 'get_public_item_schema' ), ) ); register_rest_route( $this->namespace, '/' . $this->rest_base . '/(?P[\w-]+)', array( 'args' => array( 'status' => array( 'description' => __( 'An alphanumeric identifier for the status.' ), 'type' => 'string', ), ), array( 'methods' => WP_REST_Server::READABLE, 'callback' => array( $this, 'get_item' ), 'permission_callback' => array( $this, 'get_item_permissions_check' ), 'args' => array( 'context' => $this->get_context_param( array( 'default' => 'view' ) ), ), ), 'schema' => array( $this, 'get_public_item_schema' ), ) ); } /** * Checks whether a given request has permission to read post statuses. * * @since 4.7.0 * * @param WP_REST_Request $request Full details about the request. * @return true|WP_Error True if the request has read access, WP_Error object otherwise. */ public function get_items_permissions_check( $request ) { if ( 'edit' === $request['context'] ) { $types = get_post_types( array( 'show_in_rest' => true ), 'objects' ); foreach ( $types as $type ) { if ( current_user_can( $type->cap->edit_posts ) ) { return true; } } return new WP_Error( 'rest_cannot_view', __( 'Sorry, you are not allowed to manage post statuses.' ), array( 'status' => rest_authorization_required_code() ) ); } return true; } /** * Retrieves all post statuses, depending on user context. * * @since 4.7.0 * * @param WP_REST_Request $request Full details about the request. * @return WP_REST_Response|WP_Error Response object on success, or WP_Error object on failure. */ public function get_items( $request ) { $data = array(); $statuses = get_post_stati( array( 'internal' => false ), 'object' ); $statuses['trash'] = get_post_status_object( 'trash' ); foreach ( $statuses as $obj ) { $ret = $this->check_read_permission( $obj ); if ( ! $ret ) { continue; } $status = $this->prepare_item_for_response( $obj, $request ); $data[ $obj->name ] = $this->prepare_response_for_collection( $status ); } return rest_ensure_response( $data ); } /** * Checks if a given request has access to read a post status. * * @since 4.7.0 * * @param WP_REST_Request $request Full details about the request. * @return true|WP_Error True if the request has read access for the item, WP_Error object otherwise. */ public function get_item_permissions_check( $request ) { $status = get_post_status_object( $request['status'] ); if ( empty( $status ) ) { return new WP_Error( 'rest_status_invalid', __( 'Invalid status.' ), array( 'status' => 404 ) ); } $check = $this->check_read_permission( $status ); if ( ! $check ) { return new WP_Error( 'rest_cannot_read_status', __( 'Cannot view status.' ), array( 'status' => rest_authorization_required_code() ) ); } return true; } /** * Checks whether a given post status should be visible. * * @since 4.7.0 * * @param object $status Post status. * @return bool True if the post status is visible, otherwise false. */ protected function check_read_permission( $status ) { if ( true === $status->public ) { return true; } if ( false === $status->internal || 'trash' === $status->name ) { $types = get_post_types( array( 'show_in_rest' => true ), 'objects' ); foreach ( $types as $type ) { if ( current_user_can( $type->cap->edit_posts ) ) { return true; } } } return false; } /** * Retrieves a specific post status. * * @since 4.7.0 * * @param WP_REST_Request $request Full details about the request. * @return WP_REST_Response|WP_Error Response object on success, or WP_Error object on failure. */ public function get_item( $request ) { $obj = get_post_status_object( $request['status'] ); if ( empty( $obj ) ) { return new WP_Error( 'rest_status_invalid', __( 'Invalid status.' ), array( 'status' => 404 ) ); } $data = $this->prepare_item_for_response( $obj, $request ); return rest_ensure_response( $data ); } /** * Prepares a post status object for serialization. * * @since 4.7.0 * @since 5.9.0 Renamed `$status` to `$item` to match parent class for PHP 8 named parameter support. * * @param stdClass $item Post status data. * @param WP_REST_Request $request Full details about the request. * @return WP_REST_Response Post status data. */ public function prepare_item_for_response( $item, $request ) { // Restores the more descriptive, specific name for use within this method. $status = $item; $fields = $this->get_fields_for_response( $request ); $data = array(); if ( in_array( 'name', $fields, true ) ) { $data['name'] = $status->label; } if ( in_array( 'private', $fields, true ) ) { $data['private'] = (bool) $status->private; } if ( in_array( 'protected', $fields, true ) ) { $data['protected'] = (bool) $status->protected; } if ( in_array( 'public', $fields, true ) ) { $data['public'] = (bool) $status->public; } if ( in_array( 'queryable', $fields, true ) ) { $data['queryable'] = (bool) $status->publicly_queryable; } if ( in_array( 'show_in_list', $fields, true ) ) { $data['show_in_list'] = (bool) $status->show_in_admin_all_list; } if ( in_array( 'slug', $fields, true ) ) { $data['slug'] = $status->name; } if ( in_array( 'date_floating', $fields, true ) ) { $data['date_floating'] = $status->date_floating; } $context = ! empty( $request['context'] ) ? $request['context'] : 'view'; $data = $this->add_additional_fields_to_object( $data, $request ); $data = $this->filter_response_by_context( $data, $context ); $response = rest_ensure_response( $data ); $rest_url = rest_url( rest_get_route_for_post_type_items( 'post' ) ); if ( 'publish' === $status->name ) { $response->add_link( 'archives', $rest_url ); } else { $response->add_link( 'archives', add_query_arg( 'status', $status->name, $rest_url ) ); } /** * Filters a post status returned from the REST API. * * Allows modification of the status data right before it is returned. * * @since 4.7.0 * * @param WP_REST_Response $response The response object. * @param object $status The original post status object. * @param WP_REST_Request $request Request used to generate the response. */ return apply_filters( 'rest_prepare_status', $response, $status, $request ); } /** * Retrieves the post status' schema, conforming to JSON Schema. * * @since 4.7.0 * * @return array Item schema data. */ public function get_item_schema() { if ( $this->schema ) { return $this->add_additional_fields_schema( $this->schema ); } $schema = array( '$schema' => 'http://json-schema.org/draft-04/schema#', 'title' => 'status', 'type' => 'object', 'properties' => array( 'name' => array( 'description' => __( 'The title for the status.' ), 'type' => 'string', 'context' => array( 'embed', 'view', 'edit' ), 'readonly' => true, ), 'private' => array( 'description' => __( 'Whether posts with this status should be private.' ), 'type' => 'boolean', 'context' => array( 'edit' ), 'readonly' => true, ), 'protected' => array( 'description' => __( 'Whether posts with this status should be protected.' ), 'type' => 'boolean', 'context' => array( 'edit' ), 'readonly' => true, ), 'public' => array( 'description' => __( 'Whether posts of this status should be shown in the front end of the site.' ), 'type' => 'boolean', 'context' => array( 'view', 'edit' ), 'readonly' => true, ), 'queryable' => array( 'description' => __( 'Whether posts with this status should be publicly-queryable.' ), 'type' => 'boolean', 'context' => array( 'view', 'edit' ), 'readonly' => true, ), 'show_in_list' => array( 'description' => __( 'Whether to include posts in the edit listing for their post type.' ), 'type' => 'boolean', 'context' => array( 'edit' ), 'readonly' => true, ), 'slug' => array( 'description' => __( 'An alphanumeric identifier for the status.' ), 'type' => 'string', 'context' => array( 'embed', 'view', 'edit' ), 'readonly' => true, ), 'date_floating' => array( 'description' => __( 'Whether posts of this status may have floating published dates.' ), 'type' => 'boolean', 'context' => array( 'view', 'edit' ), 'readonly' => true, ), ), ); $this->schema = $schema; return $this->add_additional_fields_schema( $this->schema ); } /** * Retrieves the query params for collections. * * @since 4.7.0 * * @return array Collection parameters. */ public function get_collection_params() { return array( 'context' => $this->get_context_param( array( 'default' => 'view' ) ), ); } } Why Exodus Still Feels Like the Best “Pretty” Multicurrency Wallet for Casual Traders - Dr. Kamlesh Badonia
+91 83493 23292 / +91 91791 97642
Schedule a Consultation
Schedule a Consultation

Why Exodus Still Feels Like the Best “Pretty” Multicurrency Wallet for Casual Traders

  • Home
  • Blog
  • Details
  • Why Exodus Still Feels Like the Best “Pretty” Multicurrency Wallet for Casual Traders

Whoa. I opened Exodus the first time and thought, this actually looks…nice. Really. The interface matters. For many people, crypto is intimidating, and a wallet that doesn’t look like a terminal makes a big difference. My instinct said—if I can get comfortable here, maybe others will too. That gut reaction mattered more than the spec sheet.

Okay, so check this out—Exodus is a desktop and mobile multicurrency wallet that bundles a built-in exchange and a portfolio tracker into a single, visually polished app. It’s not meant for ultra-high-security institutional custody, though. Instead, it aims at the person who wants one place to hold different coins, swap between them without hopping to an exchange, and watch the value move on a clean dashboard.

Here’s what I like about it. The UX is consistent across platforms. Animations are subtle, the balance displays are clear, and the charts aren’t trying to blind you with data. There’s a simplicity to the onboarding that reduces friction for someone who’s used to banking apps. That matters—seriously—because a lot of wallets feel like they were designed by engineers for engineers. Exodus doesn’t.

Screenshot of Exodus wallet portfolio interface showing multiple assets and simple charts

Where the Built-in Exchange and Portfolio Tracker Shine

The in-app exchange is convenient. Want to swap some BTC for ETH? You can do that without leaving the wallet. Fees are baked into the rate, so it’s not always the cheapest route compared to order-book exchanges, but it’s fast and frictionless. My takeaway: use the swap for small, convenience trades; use an order-book exchange for larger, price-sensitive moves.

About the portfolio tracker—it’s simple and honest. You get a snapshot of holdings, price changes, allocation percentages, and a timeline of gains or losses. It’s not TradingView-level analysis, and it doesn’t pretend to be. Instead, it makes portfolio monitoring approachable for someone who checks once a day while sipping coffee. If you care about beautiful, easy tracking, Exodus delivers.

Initially I thought that a pretty UI might be smoke and mirrors, but then I realized the team iterated on usability for years; it’s not just skin-deep. The underlying trade-offs are deliberate: they prioritize accessibility over raw configurability. On one hand that’s great for new users—on the other hand advanced traders may find it limiting.

Security—let’s be frank. Private keys stay on your device. You control the seed phrase. There’s support for hardware wallets (Trezor integration), which is a good bridge for folks who like the Exodus interface but want that extra cold-storage assurance. I’m not 100% into touting any single app as flawless; Exodus had issues in the past with updates and support speed, though they’ve addressed many pain points. So yeah—do your backups, secure your seed, and consider hardware for big balances.

Something bugs me about ecosystems that lock you in. Exodus tries to be an ecosystem but lets you export your seed and move on. I appreciate that. (Oh, and by the way… the support docs are decent, though not exhaustive.)

Fees deserve a short aside. Transaction fees on-chain vary with network congestion—Exodus shows suggested fee options. Swap fees are part of the quote. That means you should compare rates if you’re moving large sums. Also, tax reporting: Exodus gives you the data, but you’ll probably export CSVs to a tax tool. It’s not automatic tax compliance, just raw info.

Another nuance: coin support keeps growing, but it’s uneven. Major coins and many ERC-20 tokens are supported, but very new tokens or obscure chains may be missing. If you collect niche altcoins, double-check compatibility before sending funds. The wallet will warn you on unsupported assets, but mistakes happen—so be careful.

I’ll be honest—customer service used to be slow. Now, it’s better, though still not instant like a bank chat. If you need help recovering a wallet, Exodus provides a recovery flow, but the speed and clarity of that help is variable. So plan ahead. Back up your recovery phrase immediately.

Something felt off about recommending any single solution to everyone. Different users have different priorities. If you prioritize ease of use and an integrated portfolio view, Exodus is a top pick. If atomic anonymity, deep configurability, or the cheapest swap rates are your thing, you’ll want other tools too.

Quick Practical Tips (so you don’t learn the hard way)

– Back up the 12-word phrase and store it offline. Do not screenshot it. Seriously.
– For larger balances, pair Exodus with a hardware wallet. Use Exodus for day-to-day viewing, Trezor for cold storage.
– Compare swap rates for big trades. In small amounts, the convenience trade-off is often worth it.
– Double-check addresses for new coins. If you send the wrong chain, the funds may be unrecoverable.

If you want a closer look or official guides, you can check their pages here: https://sites.google.com/walletcryptoextension.com/exodus-wallet/. It’s a decent starting point for learning how the app organizes assets and swaps.

FAQ

Is Exodus safe for beginners?

Yes, relative to many competitors. It stores keys locally and is easy to back up. But “safe” depends on user practices—if someone loses their seed phrase or runs malware, any wallet becomes risky. For small to medium balances it’s a solid choice.

Can I use Exodus for day trading?

Technically yes, but it’s not optimized for active traders. The built-in swap is convenient, but you won’t get order-book depth or advanced order types. For frequent trading, pair Exodus with an exchange account and move funds as needed.

Does Exodus support hardware wallets?

Yes—Exodus supports Trezor integration, so you can combine Exodus’s UI with Trezor’s hardware security for safer key storage.

Alright—closing thought. Exodus isn’t perfect. It doesn’t try to be Everything. Some parts of the app are delightful, others less so. If you want a clean, approachable multicurrency wallet with an integrated exchange and portfolio view, it’s earned its place on the shortlist. Try it with a small amount first, form your own opinion, and then decide where to keep the heavy stuff.

Leave A Comment

Your email address will not be published *